/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_userdb (2973B)
pam_userdb -- PAM module to authenticate against a db database -------------------------------------------------------------------------- DESCRIPTION The pam_userdb module is used to verify a username/password pair against values stored in a Berkeley DB database. The database is indexed by the username, and the data fields corresponding to the username keys are the passwords. OPTIONS crypt=[crypt|none] Indicates whether encrypted or plaintext passwords are stored in the database. If it is crypt, passwords should be stored in the database in crypt(3) form. If none is selected, passwords should be stored in the database as plaintext. db=/path/database Use the /path/database database for performing lookup. There is no default; the module will return PAM_IGNORE if no database is provided. Note that the path to the database file should be specified without the .db suffix. debug Print debug information. Note that password hashes, both from db and computed, will be printed to syslog. dump Dump all the entries in the database to the log. Don't do this by default! icase Make the password verification to be case insensitive (ie when working with registration numbers and such). Only works with plaintext password storage. try_first_pass Use the authentication token previously obtained by another module that did the conversation with the application. If this token can not be obtained then the module will try to converse. This option can be used for stacking different modules that need to deal with the authentication tokens. use_first_pass Use the authentication token previously obtained by another module that did the conversation with the application. If this token can not be obtained then the module will fail. This option can be used for stacking different modules that need to deal with the authentication tokens. unknown_ok Do not return error when checking for a user that is not in the database. This can be used to stack more than one pam_userdb module that will check a username/password pair in more than a database. key_only The username and password are concatenated together in the database hash as 'username-password' with a random value. if the concatenation of the username and password with a dash in the middle returns any result, the user is valid. this is useful in cases where the username may not be unique but the username and password pair are. EXAMPLES auth sufficient pam_userdb.so icase db=/etc/dbtest AUTHOR pam_userdb was written by Cristian Gafton >gafton@redhat.com<.