From: Thorsten Kukuk Date: Thu, 29 Jan 2009 11:44:08 +0000 (+0000) Subject: Relevant BUGIDs: X-Git-Tag: Linux-PAM-1_0_91~13 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=50015536b9f48cc6b916465730e1fb5214f1fda6;p=linux-pam Relevant BUGIDs: Purpose of commit: bugfix Commit summary: --------------- 2009-01-29 Thorsten Kukuk * doc/man/pam_sm_setcred.3.xml: Document PAM_ESTABLISHED_CRED. --- diff --git a/ChangeLog b/ChangeLog index a00752cd..ee3ba8ec 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2009-01-29 Thorsten Kukuk + + * doc/man/pam_sm_setcred.3.xml: Document PAM_ESTABLISHED_CRED. + 2009-01-19 Tomas Mraz * modules/pam_mkhomedir/Makefile.am: Add mkhomedir_helper. diff --git a/doc/man/pam_sm_setcred.3.xml b/doc/man/pam_sm_setcred.3.xml index e4809ad7..e557000c 100644 --- a/doc/man/pam_sm_setcred.3.xml +++ b/doc/man/pam_sm_setcred.3.xml @@ -61,6 +61,12 @@ + + PAM_ESTABLISH_CRED + + Initialize the credentials for the user. + + PAM_DELETE_CRED @@ -87,15 +93,15 @@ - The way the auth stack is + The way the auth stack is navigated in order to evaluate the pam_setcred() - function call, independent of the pam_sm_setcred() + function call, independent of the pam_sm_setcred() return codes, is exactly the same way that it was navigated when evaluating the pam_authenticate() library call. Typically, if a stack entry was ignored in evaluating pam_authenticate(), it will be ignored when - libpam evaluates the pam_setcred() function - call. Otherwise, the return codes from each module specific + libpam evaluates the pam_setcred() function + call. Otherwise, the return codes from each module specific pam_sm_setcred() call are treated as required. @@ -146,9 +152,9 @@ - These, non-PAM_SUCCESS, return values will + These, non-PAM_SUCCESS, return values will typically lead to the credential stack failing. - The first such error will dominate in the return value of + The first such error will dominate in the return value of pam_setcred().