| PAM_DIAL_AUTH(7) | Standards, Environments, and Macros | PAM_DIAL_AUTH(7) |
pam_dial_auth - authentication management PAM module for dialups
pam_dial_auth.so.1
The pam_dial_auth module implements pam_sm_authenticate(3PAM) which authenticates the user according to the dialups(5) and d_passwd(5) files configuration.
Authentication service modules must implement both pam_sm_authenticate() and pam_sm_setcred(). pam_sm_setcred() in this module always returns PAM_IGNORE.
The value of the PAM_TTY item is checked against entries in dialups(5). If there is a match, the user's shell is compared against entries in d_passwd(5). If there is a matching entry, the user is prompted for a password which is validated against the entry found.
The following option may be passed in to this service module:
debug
If dialups(5) is not present, PAM_IGNORE is returned. Upon successful completion of pam_sm_authenticate(), PAM_SUCCESS is returned. The following error codes are returned upon error:
PAM_AUTH_ERR
PAM_SERVICE_ERR
PAM_SYSTEM_ERR
PAM_USER_UNKNOWN
See attributes(7) for a description of the following attributes:
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
| MT Level | MT-Safe with exceptions |
libpam(3LIB), pam(3PAM), pam_authenticate(3PAM), pam_sm_authenticate(3PAM), d_passwd(5), dialups(5), pam.conf(5), attributes(7), pam_authtok_check(7), pam_authtok_get(7), pam_authtok_store(7), pam_dhkeys(7), pam_passwd_auth(7), pam_unix_account(7), pam_unix_auth(7), pam_unix_session(7)
The interfaces in libpam(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own PAM handle.
The pam_unix(7) module is no longer supported. Similar functionality is provided by pam_authtok_check(7), pam_authtok_get(7), pam_authtok_store(7), pam_dhkeys(7), pam_passwd_auth(7), pam_unix_account(7), pam_unix_auth(7), and pam_unix_session(7).
| September 9, 2004 | OmniOS |