kapabilities
Pupeno <[email protected]>
| Newsgroups | gmane.linux.arklinux.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As I was about to develop the user management tool that should be able to manage kapabilities, I checked how kapabilities work and I have a suggestion. Why instead of modifing the pam.d files, we make pam.d files static and modify /etc/group... For example, this would work this way: one time of access would be "User management" then we make a user group (on /etc/group) called usermanagement (or um or whatever) and then we make: /etc/pam.d/kuser:auth sufficient /lib/security/pam_userlist.so groups=usermanagement /etc/pam.d/arkusermanagementtool:auth sufficient /lib/security/pam_userlist.so groups=usermanaagement /etc/pam.d/anothertool:auth sufficient /lib/security/pam_userlist.so groups=usermanaagement and then, to allow a user to do user management we just add it to the User management group on /etc/group am I wrong ? did I missed something ? BTW, if I go to kcontrol -> System Administration -> Login Manager and I press the Administration button it doesn't ask me for a password ? why ? I mean, from a software point of view, what allows me to go passwordless there ? Thanks. - -- Pupeno: [email protected] http://www.pupeno.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAELB3tCepaMf3unIRAlmMAJwMLRDbbzhbz6fDIiNNz6nD6O/LEQCfX8w0 lgqKbiWV8N9d4nmpQZMbeXY= =bKEc -----END PGP SIGNATURE-----