The dialup PAM module, /usr/lib/security/pam_dial_auth.so.1, authenticates a user according to the /etc/dialups and /etc/d_passwd files. Only pam_sm_authenticate() is implemented within this module. pam_sm_setcred() is a null function. /usr/lib/security/pam_dial_auth.so.1 is designed to be stacked immediately below the /usr/lib/security/pam_unix.so.1 module for the login service.

pam_sm_authenticate() performs authentication only if both the /etc/dialups and /etc/d_passwd files exist. The user's terminal line is checked against entries in the /etc/dialups file. If there is a match, the user's shell is compared against entries in the /etc/d_passwd file. If there is a matching entry, the user is prompted for a password which is validated against the entry in the /etc/d_passwd file. If the passwords match, the user is authenticated. The following option may be passed in to this service module:

debug

syslog(3C) debugging information at LOG_DEBUG level.

See attributes(5) for description of the following attributes:

pam(3PAM), pam_authenticate(3PAM), d_passwd(4), dialups(4), libpam(3LIB), pam.conf(4), attributes(5), pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix(5), pam_unix_account(5), pam_unix_auth(5), pam_unix_session(5)

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(5) module might not be supported in a future release. Similar functionality is provided by pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5), and pam_unix_session(5).