diff options
Diffstat (limited to 'modules/pam_userdb/pam_userdb.8')
| -rw-r--r-- | modules/pam_userdb/pam_userdb.8 | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/modules/pam_userdb/pam_userdb.8 b/modules/pam_userdb/pam_userdb.8 index fc002787..c6397723 100644 --- a/modules/pam_userdb/pam_userdb.8 +++ b/modules/pam_userdb/pam_userdb.8 @@ -1,13 +1,13 @@ '\" t .\" Title: pam_userdb .\" Author: [see the "AUTHOR" section] -.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/> -.\" Date: 09/03/2021 +.\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/> +.\" Date: 05/07/2023 .\" Manual: Linux-PAM Manual -.\" Source: Linux-PAM Manual +.\" Source: Linux-PAM .\" Language: English .\" -.TH "PAM_USERDB" "8" "09/03/2021" "Linux-PAM Manual" "Linux\-PAM Manual" +.TH "PAM_USERDB" "8" "05/07/2023" "Linux\-PAM" "Linux\-PAM Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -37,7 +37,7 @@ pam_userdb \- PAM module to authenticate against a db database 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\&. .SH "OPTIONS" .PP -\fBcrypt=[crypt|none]\fR +crypt=[crypt|none] .RS 4 Indicates whether encrypted or plaintext passwords are stored in the database\&. If it is \fBcrypt\fR, passwords should be stored in the database in @@ -47,7 +47,7 @@ form\&. If is selected, passwords should be stored in the database as plaintext\&. .RE .PP -\fBdb=\fR\fB\fI/path/database\fR\fR +db=/path/database .RS 4 Use the /path/database @@ -58,37 +58,37 @@ if no database is provided\&. Note that the path to the database file should be suffix\&. .RE .PP -\fBdebug\fR +debug .RS 4 Print debug information\&. Note that password hashes, both from db and computed, will be printed to syslog\&. .RE .PP -\fBdump\fR +dump .RS 4 Dump all the entries in the database to the log\&. Don\*(Aqt do this by default! .RE .PP -\fBicase\fR +icase .RS 4 Make the password verification to be case insensitive (ie when working with registration numbers and such)\&. Only works with plaintext password storage\&. .RE .PP -\fBtry_first_pass\fR +try_first_pass .RS 4 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\&. .RE .PP -\fBuse_first_pass\fR +use_first_pass .RS 4 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\&. .RE .PP -\fBunknown_ok\fR +unknown_ok .RS 4 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\&. .RE .PP -\fBkey_only\fR +key_only .RS 4 The username and password are concatenated together in the database hash as \*(Aqusername\-password\*(Aq 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\&. .RE |