1pam_dial_auth(5) Standards, Environments, and Macros pam_dial_auth(5)
2
3
4
6 pam_dial_auth - authentication management PAM module for dialups
7
9 pam_dial_auth.so.1
10
11
13 The pam_dial_auth module implements pam_sm_authenticate(3PAM) which
14 authenticates the user according to the dialups(4) and d_passwd(4)
15 files configuration.
16
17
18 Authentication service modules must implement both pam_sm_authenti‐
19 cate() and pam_sm_setcred(). pam_sm_setcred() in this module always
20 returns PAM_IGNORE.
21
22
23 The value of the PAM_TTY item is checked against entries in dialups(4).
24 If there is a match, the user's shell is compared against entries in
25 d_passwd(4). If there is a matching entry, the user is prompted for a
26 password which is validated against the entry found.
27
28
29 The following option may be passed in to this service module:
30
31 debug syslog(3C) debugging information at LOG_DEBUG level.
32
33
35 If dialups(4) is not present, PAM_IGNORE is returned. Upon successful
36 completion of pam_sm_authenticate(), PAM_SUCCESS is returned. The fol‐
37 lowing error codes are returned upon error:
38
39 PAM_AUTH_ERR Authentication failure.
40
41
42 PAM_SERVICE_ERR Error in the calling service, PAM_TTY is not set.
43
44
45 PAM_SYSTEM_ERR System error (d_passwd(4) is not present).
46
47
48 PAM_USER_UNKNOWN No account is present for user.
49
50
52 See attributes(5) for a description of the following attributes:
53
54
55
56
57 ┌─────────────────────────────┬─────────────────────────────┐
58 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
59 ├─────────────────────────────┼─────────────────────────────┤
60 │MT Level │MT-Safe with exceptions │
61 └─────────────────────────────┴─────────────────────────────┘
62
64 pam(3PAM), pam_authenticate(3PAM), pam_sm_authenticate(3PAM),
65 d_passwd(4), dialups(4), libpam(3LIB), pam.conf(4), attributes(5),
66 pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5),
67 pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5),
68 pam_unix_auth(5), pam_unix_session(5)
69
71 The interfaces in libpam(3LIB) are MT-Safe only if each thread within
72 the multi-threaded application uses its own PAM handle.
73
74
75 The pam_unix(5) module is no longer supported. Similar functionality is
76 provided by pam_authtok_check(5), pam_authtok_get(5), pam_auth‐
77 tok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5),
78 pam_unix_auth(5), and pam_unix_session(5).
79
80
81
82SunOS 5.11 9 Sept 2004 pam_dial_auth(5)