From d48c90b14254794fcad9ccc37873a8c663cce02d Mon Sep 17 00:00:00 2001 From: Thorsten Kukuk Date: Tue, 8 Jan 2008 12:44:15 +0000 Subject: Relevant BUGIDs: Purpose of commit: cleanup Commit summary: --------------- Remove autogenerated documentation from CVS --- modules/pam_userdb/.cvsignore | 2 + modules/pam_userdb/README | 74 ---------------------------- modules/pam_userdb/pam_userdb.8 | 104 ---------------------------------------- 3 files changed, 2 insertions(+), 178 deletions(-) delete mode 100644 modules/pam_userdb/README delete mode 100644 modules/pam_userdb/pam_userdb.8 (limited to 'modules/pam_userdb') diff --git a/modules/pam_userdb/.cvsignore b/modules/pam_userdb/.cvsignore index 9fb98574..ca9670ba 100644 --- a/modules/pam_userdb/.cvsignore +++ b/modules/pam_userdb/.cvsignore @@ -4,3 +4,5 @@ .libs Makefile Makefile.in +README +pam_userdb.8 diff --git a/modules/pam_userdb/README b/modules/pam_userdb/README deleted file mode 100644 index 8e1a5ffd..00000000 --- a/modules/pam_userdb/README +++ /dev/null @@ -1,74 +0,0 @@ -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. - -debug - - Print debug information. - -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.db - - -AUTHOR - -pam_userdb was written by Cristian Gafton >gafton@redhat.com<. - diff --git a/modules/pam_userdb/pam_userdb.8 b/modules/pam_userdb/pam_userdb.8 deleted file mode 100644 index b1ad6677..00000000 --- a/modules/pam_userdb/pam_userdb.8 +++ /dev/null @@ -1,104 +0,0 @@ -.\" Title: pam_userdb -.\" Author: -.\" Generator: DocBook XSL Stylesheets v1.70.1 -.\" Date: 06/07/2006 -.\" Manual: Linux\-PAM Manual -.\" Source: Linux\-PAM Manual -.\" -.TH "PAM_USERDB" "8" "06/07/2006" "Linux\-PAM Manual" "Linux\-PAM Manual" -.\" disable hyphenation -.nh -.\" disable justification (adjust text to left margin only) -.ad l -.SH "NAME" -pam_userdb \- PAM module to authenticate against a db database -.SH "SYNOPSIS" -.HP 14 -\fBpam_userdb.so\fR db=\fI/path/database\fR [debug] [crypt=[crypt|none]] [icase] [dump] [try_first_pass] [use_first_pass] [unknown_ok] [key_only] -.SH "DESCRIPTION" -.PP -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" -.TP 3n -\fBcrypt=[crypt|none]\fR -Indicates whether encrypted or plaintext passwords are stored in the database. If it is -\fBcrypt\fR, passwords should be stored in the database in -\fBcrypt\fR(3) -form. If -\fBnone\fR -is selected, passwords should be stored in the database as plaintext. -.TP 3n -\fBdb=\fR\fB\fI/path/database\fR\fR -Use the -\fI/path/database\fR -database for performing lookup. There is no default; the module will return -\fBPAM_IGNORE\fR -if no database is provided. -.TP 3n -\fBdebug\fR -Print debug information. -.TP 3n -\fBdump\fR -Dump all the entries in the database to the log. Don't do this by default! -.TP 3n -\fBicase\fR -Make the password verification to be case insensitive (ie when working with registration numbers and such). Only works with plaintext password storage. -.TP 3n -\fBtry_first_pass\fR -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. -.TP 3n -\fBuse_first_pass\fR -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. -.TP 3n -\fBunknown_ok\fR -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. -.TP 3n -\fBkey_only\fR -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. -.SH "MODULE SERVICES PROVIDED" -.PP -The services -\fBauth\fR -and -\fBaccount\fR -are supported. -.SH "RETURN VALUES" -.TP 3n -PAM_AUTH_ERR -Authentication failure. -.TP 3n -PAM_AUTHTOK_RECOVERY_ERR -Authentication information cannot be recovered. -.TP 3n -PAM_BUF_ERR -Memory buffer error. -.TP 3n -PAM_CONV_ERR -Conversation failure. -.TP 3n -PAM_SERVICE_ERR -Error in service module. -.TP 3n -PAM_SUCCESS -Success. -.TP 3n -PAM_USER_UNKNOWN -User not known to the underlying authentication module. -.SH "EXAMPLES" -.sp -.RS 3n -.nf -auth sufficient pam_userdb.so icase db=/etc/dbtest.db - -.fi -.RE -.SH "SEE ALSO" -.PP - -\fBcrypt\fR(3), -\fBpam.conf\fR(5), -\fBpam.d\fR(8), -\fBpam\fR(8) -.SH "AUTHOR" -.PP -pam_userdb was written by Cristian Gafton >gafton@redhat.com<. -- cgit v1.2.3