/usr/share/doc/pam/txts
NameSizeModeActions
README.pam_access52530644editdlrm
README.pam_chroot15100644editdlrm
README.pam_console19250644editdlrm
README.pam_cracklib97570644editdlrm
README.pam_debug19950644editdlrm
README.pam_deny10350644editdlrm
README.pam_echo11000644editdlrm
README.pam_env36270644editdlrm
README.pam_exec22300644editdlrm
README.pam_faildelay8270644editdlrm
README.pam_faillock60620644editdlrm
README.pam_filter31020644editdlrm
README.pam_ftp16990644editdlrm
README.pam_group21750644editdlrm
README.pam_issue13560644editdlrm
README.pam_keyinit22450644editdlrm
README.pam_lastlog25970644editdlrm
README.pam_limits24210644editdlrm
README.pam_listfile36260644editdlrm
README.pam_localuser11670644editdlrm
README.pam_loginuid11170644editdlrm
README.pam_mail20090644editdlrm
README.pam_mkhomedir13610644editdlrm
README.pam_motd25880644editdlrm
README.pam_namespace115430644editdlrm
README.pam_nologin13480644editdlrm
README.pam_permit9070644editdlrm
README.pam_postgresok3460644editdlrm
README.pam_pwhistory22430644editdlrm
README.pam_rhosts18820644editdlrm
README.pam_rootok10860644editdlrm
README.pam_securetty13420644editdlrm
README.pam_selinux29090644editdlrm
README.pam_sepermit16480644editdlrm
README.pam_shells6530644editdlrm
README.pam_stress20600644editdlrm
README.pam_succeed_if28640644editdlrm
README.pam_time13010644editdlrm
README.pam_timestamp16160644editdlrm
README.pam_tty_audit27790644editdlrm
README.pam_umask16310644editdlrm
README.pam_unix72650644editdlrm
README.pam_userdb29730644editdlrm
README.pam_usertype12000644editdlrm
README.pam_warn12240644editdlrm
README.pam_wheel19680644editdlrm
README.pam_xauth36950644editdlrm
Edit: /usr/share/doc/pam/txts/README.pam_group (2175B)
pam_group — PAM module for group access ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DESCRIPTION The pam_group PAM module does not authenticate the user, but instead it grants group memberships (in the credential setting phase of the authentication module) to the user. Such memberships are based on the service they are applying for. By default rules for group memberships are taken from config file /etc/security /group.conf. This module's usefulness relies on the file-systems accessible to the user. The point being that once granted the membership of a group, the user may attempt to create a setgid binary with a restricted group ownership. Later, when the user is not given membership to this group, they can recover group membership with the precompiled binary. The reason that the file-systems that the user has access to are so significant, is the fact that when a system is mounted nosuid the user is unable to create or execute such a binary file. For this module to provide any level of security, all file-systems that the user has write access to should be mounted nosuid. The pam_group module functions in parallel with the /etc/group file. If the user is granted any groups based on the behavior of this module, they are granted in addition to those entries /etc/group (or equivalent). EXAMPLES These are some example lines which might be specified in /etc/security/ group.conf. Running 'xsh' on tty* (any ttyXXX device), the user 'us' is given access to the floppy (through membership of the floppy group) xsh;tty*&!ttyp*;us;Al0000-2400;floppy Running 'xsh' on tty* (any ttyXXX device), the users 'sword', 'pike' and 'shield' are given access to games (through membership of the floppy group) after work hours. xsh; tty* ;sword|pike|shield;!Wk0900-1800;games, sound xsh; tty* ;*;Al0900-1800;floppy Any member of the group 'admin' running 'xsh' on tty*, is granted access (at any time) to the group 'plugdev' xsh; tty* ;%admin;Al0000-2400;plugdev