OK. Sudo-ldap was 1.8.31 still. For the sudo-rbac, I'll need to build a new one.
The key elements: sudo is not SUID (root), it is 'just an application' - that I setup to be owned by 'sudo' - and it runs, under the covers, as SUID (sudo) so that it can read and edit the sudo-config files.
From my presentation - in 2017 - I have this as the basic setup after installation:
mkauth sudo
setkst
mkrole authorizations='sudo' dfltmsg='sudoers role' sudoers
setkst
setsecattr -c accessauths=sudo innateprivs=PV_DAC_GID,PV_DAC_R inheritprivs=PV_ROOT secflags=FSF_EPS /opt/bin/sudo
setkst
chmod og-rwx /opt/bin/sudo
mkuser roles=sudoers michael
pwdadm michael
Changing password for "michael"
michael's New password:
Setting "michael's" password to NULL.
As root: add michael as a sudoer
vi /var/sudo-rbac/etc/sudoers
# add michael as test user
michael ALL=(ALL) ALL
And working with sudo - as michael:
ls -l /opt/bin/sudo
-rws------ 1 bin bin 431763 Sep 25 20:42 /opt/bin/sudo
sudo ls /etc/security
ksh: sudo: 0403-006 Execute permission denied.
michael@x065:[/home/michael]swrole sudoers
michael's Password:
michael@x065:[/home/michael]sudo ls /etc/security
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
acl domains ice mkuser.default privcmds pwdhist.dir smitacl.user user.roles
aixpert domobjs lastlog mkuser.sys privcmds.backup pwdhist.pag sysck.cfg
audit environ ldap passwd privdevs roles tsd
authorizations fpm limits portlog privfiles services tss
certificates group login.cfg priv pwdalg.cfg smitacl.group user
michael@x065:[/home/michael]ls /etc/security
ls: /etc/security: The file access permissions do not allow the specified action.
* So, the key difference is that sudo is not SUID root - and only users with a active role can execute sudo.
* that is, if you do not have the role to access sudo - you cannot even probe if the setup is weak.
* without RBAC as a security mechanism - everyone can execute sudo - and it is up to the sudo configuration to stop - after the fact - unauthorized users.
* the rest of the configuration is the same