network/AD accounts in Sudoers and “bridging” products
Brian Hanrahan <[email protected]> Mon, 2 Mar 2020 11:14:26 -0500
| Newsgroups | gmane.comp.tools.sudo.user |
|---|---|
| Message-ID | <CAL+Y3Lfoip25u5vqVtJ7+v7n3B=5Uv5wntACer5tG_fN7tbFVQ@mail.gmail.com> |
Is there any practical case where user entries for network accounts (typically AD user or group) do not follow the netgroup syntax from: https://www.sudo.ws/man/1.8.31/sudoers.man.html#SUDOERS_FILE_FORMAT ? When user authentication and group membership resolution are handled by Centrify, BeyondTrust or similar is netgroup syntax still employed in Sudoers to match the (typically AD) accounts? I can't see any other way for Sudo to be secure given local and network user accounts, but it's an assumption I didn't want to make. The concern is that products implementing "directory bridging" might cause Sudo entries intended for local accounts to authorize a same-named network account. Given a Sudo entry like "Susie All(All) All" I can imagine it could be associated to susie@some_domain.org given a product's PAM module has full control Thanks in advance for any info/insight you can offer! ____________________________________________________________ sudo-users mailing list <[email protected]> For list information, options, or to unsubscribe, visit: https://www.sudo.ws/mailman/listinfo/sudo-users