Diffstat (limited to 'doc/man/pam_get_item.3')
1 files changed, 116 insertions, 1 deletions
diff --git a/doc/man/pam_get_item.3 b/doc/man/pam_get_item.3
index 06df97bb..12ce870e 100644
@@ -1 +1,116 @@
+.\" ** You probably do not want to edit this file directly **
+.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
+.\" Instead of manually editing it, you probably should edit the DocBook XML
+.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
+.TH "PAM_GET_ITEM" "3" "02/12/2006" "Linux\-PAM Manual" "Linux\-PAM Manual"
+.\" disable hyphenation
+.\" disable justification (adjust text to left margin only)
+pam_get_item \- getting PAM informations
+\fBint\ \fBpam_get_item\fR\fR\fB(\fR\fBconst\ pam_handle_t\ *\fR\fB\fIpamh\fR\fR\fB, \fR\fBint\ \fR\fB\fIitem_type\fR\fR\fB, \fR\fBconst\ void\ **\fR\fB\fIitem\fR\fR\fB);\fR
+function allows applications and PAM service modules to access and retrieve PAM informations of
+\fIitem_type\fR. Upon successful return,
+contains a pointer to the value of the corresponding item. Note, this is a pointer to the
+data and should
+\fIfree()\fR'ed or over\-written! The following values are supported for
+The service name (which identifies that PAM stack that the PAM functions will use to authenticate the program).
+The username of the entity under whose identity service will be given. That is, following authentication,
+identifies the local entity that gets to use the service. Note, this value can be mapped from something (eg., "anonymous") to something else (eg. "guest119") by any module in the PAM stack. As such an application should consult the value of
+after each call to a PAM function.
+The string used when prompting for a user's name. The default value for this string is a localized version of "login: ".
+The terminal name: prefixed by
+if it is a device file; for graphical, X\-based, applications the value for this item should be the
+The requesting user name: local name for a locally requesting user or a remote user name for a remote requesting user.
+Generally an application or module will attempt to supply the value that is most strongly authenticated (a local account before a remote one. The level of trust in this value is embodied in the actual authentication stack associated with the application, so it is ultimately at the discretion of the system administrator.
+should always identify the requesting user. In some cases,
+may be NULL. In such situations, it is unclear who the requesting entity is.
+The requesting hostname (the hostname of the machine from which the
+entity is requesting service). That is
+does identify the requesting user. In some applications,
+may be NULL. In such situations, it is unclear where the authentication request is originating from.
+The authentication token (often a password). This token should be ignored by all module functions besides
+\fBpam_sm_chauthtok\fR(3). In the former function it is used to pass the most recent authentication token from one stacked module to another. In the latter function the token is used for another purpose. It contains the currently active authentication token.
+The old authentication token. This token should be ignored by all module functions except
+The pam_conv structure. See
+A function pointer to redirect centrally managed failure delays. See
+If a service module wishes to obtain the name of the user, it should not use this function, but instead perform a call to
+Only a service module is privileged to read the authentication tokens, PAM_AUTHTOK and PAM_OLDAUTHTOK.
+.SH "RETURN VALUES"
+The application attempted to set an undefined or inaccessible item.
+Memory buffer error.
+The value of
+Data was successful updated.
+passed as first argument was invalid.
+.SH "SEE ALSO"