/
usr
/
share
/
doc
/
pam
/
txts
/
/usr/share/doc/pam/txts
mkdir
upload
Name
Size
Mode
Actions
README.pam_access
5253
0644
edit
dl
rm
README.pam_chroot
1510
0644
edit
dl
rm
README.pam_console
1925
0644
edit
dl
rm
README.pam_cracklib
9757
0644
edit
dl
rm
README.pam_debug
1995
0644
edit
dl
rm
README.pam_deny
1035
0644
edit
dl
rm
README.pam_echo
1100
0644
edit
dl
rm
README.pam_env
3627
0644
edit
dl
rm
README.pam_exec
2230
0644
edit
dl
rm
README.pam_faildelay
827
0644
edit
dl
rm
README.pam_faillock
6062
0644
edit
dl
rm
README.pam_filter
3102
0644
edit
dl
rm
README.pam_ftp
1699
0644
edit
dl
rm
README.pam_group
2175
0644
edit
dl
rm
README.pam_issue
1356
0644
edit
dl
rm
README.pam_keyinit
2245
0644
edit
dl
rm
README.pam_lastlog
2597
0644
edit
dl
rm
README.pam_limits
2421
0644
edit
dl
rm
README.pam_listfile
3626
0644
edit
dl
rm
README.pam_localuser
1167
0644
edit
dl
rm
README.pam_loginuid
1117
0644
edit
dl
rm
README.pam_mail
2009
0644
edit
dl
rm
README.pam_mkhomedir
1361
0644
edit
dl
rm
README.pam_motd
2588
0644
edit
dl
rm
README.pam_namespace
11543
0644
edit
dl
rm
README.pam_nologin
1348
0644
edit
dl
rm
README.pam_permit
907
0644
edit
dl
rm
README.pam_postgresok
346
0644
edit
dl
rm
README.pam_pwhistory
2243
0644
edit
dl
rm
README.pam_rhosts
1882
0644
edit
dl
rm
README.pam_rootok
1086
0644
edit
dl
rm
README.pam_securetty
1342
0644
edit
dl
rm
README.pam_selinux
2909
0644
edit
dl
rm
README.pam_sepermit
1648
0644
edit
dl
rm
README.pam_shells
653
0644
edit
dl
rm
README.pam_stress
2060
0644
edit
dl
rm
README.pam_succeed_if
2864
0644
edit
dl
rm
README.pam_time
1301
0644
edit
dl
rm
README.pam_timestamp
1616
0644
edit
dl
rm
README.pam_tty_audit
2779
0644
edit
dl
rm
README.pam_umask
1631
0644
edit
dl
rm
README.pam_unix
7265
0644
edit
dl
rm
README.pam_userdb
2973
0644
edit
dl
rm
README.pam_usertype
1200
0644
edit
dl
rm
README.pam_warn
1224
0644
edit
dl
rm
README.pam_wheel
1968
0644
edit
dl
rm
README.pam_xauth
3695
0644
edit
dl
rm
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<.
Save
cmd:
run