2 .\" Copyright (C) 2002, Sun Microsystems, Inc.
3 .\" All Rights Reserved
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH PAM_DIAL_AUTH 5 "Sep 9, 2004"
9 pam_dial_auth \- authentication management PAM module for dialups
13 \fBpam_dial_auth.so.1\fR
19 The \fBpam_dial_auth\fR module implements \fBpam_sm_authenticate\fR(3PAM) which
20 authenticates the user according to the \fBdialups\fR(4) and \fBd_passwd\fR(4)
24 Authentication service modules must implement both \fBpam_sm_authenticate()\fR
25 and \fBpam_sm_setcred()\fR. \fBpam_sm_setcred()\fR in this module always
26 returns \fBPAM_IGNORE\fR.
29 The value of the \fBPAM_TTY\fR item is checked against entries in
30 \fBdialups\fR(4). If there is a match, the user's shell is compared against
31 entries in \fBd_passwd\fR(4). If there is a matching entry, the user is
32 prompted for a password which is validated against the entry found.
35 The following option may be passed in to this service module:
42 \fBsyslog\fR(3C) debugging information at \fBLOG_DEBUG\fR level.
48 If \fBdialups\fR(4) is not present, \fBPAM_IGNORE\fR is returned. Upon
49 successful completion of \fBpam_sm_authenticate()\fR, \fBPAM_SUCCESS\fR is
50 returned. The following error codes are returned upon error:
54 \fB\fBPAM_AUTH_ERR\fR\fR
57 Authentication failure.
63 \fB\fBPAM_SERVICE_ERR\fR\fR
66 Error in the calling service, \fBPAM_TTY\fR is not set.
72 \fB\fBPAM_SYSTEM_ERR\fR\fR
75 System error (\fBd_passwd\fR(4) is not present).
81 \fB\fBPAM_USER_UNKNOWN\fR\fR
84 No account is present for \fIuser\fR.
90 See \fBattributes\fR(5) for a description of the following attributes:
98 ATTRIBUTE TYPE ATTRIBUTE VALUE
100 MT Level MT-Safe with exceptions
106 \fBpam\fR(3PAM), \fBpam_authenticate\fR(3PAM), \fBpam_sm_authenticate\fR(3PAM),
107 \fBd_passwd\fR(4), \fBdialups\fR(4), \fBlibpam\fR(3LIB), \fBpam.conf\fR(4),
108 \fBattributes\fR(5), \fBpam_authtok_check\fR(5), \fBpam_authtok_get\fR(5),
109 \fBpam_authtok_store\fR(5), \fBpam_dhkeys\fR(5), \fBpam_passwd_auth\fR(5),
110 \fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5), \fBpam_unix_session\fR(5)
114 The interfaces in \fBlibpam\fR(3LIB) are MT-Safe only if each thread within the
115 multi-threaded application uses its own \fBPAM\fR handle.
118 The \fBpam_unix\fR(5) module is no longer supported. Similar functionality is
119 provided by \fBpam_authtok_check\fR(5), \fBpam_authtok_get\fR(5),
120 \fBpam_authtok_store\fR(5), \fBpam_dhkeys\fR(5), \fBpam_passwd_auth\fR(5),
121 \fBpam_unix_account\fR(5), \fBpam_unix_auth\fR(5), and
122 \fBpam_unix_session\fR(5).