1PAM_ACCESS(8)                  Linux-PAM Manual                  PAM_ACCESS(8)
2
3
4

NAME

6       pam_access - PAM module for logdaemon style login access control
7

SYNOPSIS

9       pam_access.so [debug] [nodefgroup] [noaudit] [accessfile=file]
10                     [fieldsep=sep] [listsep=sep]
11

DESCRIPTION

13       The pam_access PAM module is mainly for access management. It provides
14       logdaemon style login access control based on login names, host or
15       domain names, internet addresses or network numbers, or on terminal
16       line names, X $DISPLAY values, or PAM service names in case of
17       non-networked logins.
18
19       By default rules for access management are taken from config file
20       /etc/security/access.conf if you don't specify another file. Then
21       individual *.conf files from the /etc/security/access.d/ directory are
22       read. The files are parsed one after another in the order of the system
23       locale. The effect of the individual files is the same as if all the
24       files were concatenated together in the order of parsing. This means
25       that once a pattern is matched in some file no further files are
26       parsed. If a config file is explicitly specified with the accessfile
27       option the files in the above directory are not parsed.
28
29       If Linux PAM is compiled with audit support the module will report when
30       it denies access based on origin (host, tty, etc.).
31

OPTIONS

33       accessfile=/path/to/access.conf
34           Indicate an alternative access.conf style configuration file to
35           override the default. This can be useful when different services
36           need different access lists.
37
38       debug
39           A lot of debug information is printed with syslog(3).
40
41       noaudit
42           Do not report logins from disallowed hosts and ttys to the audit
43           subsystem.
44
45       fieldsep=separators
46           This option modifies the field separator character that pam_access
47           will recognize when parsing the access configuration file. For
48           example: fieldsep=| will cause the default `:' character to be
49           treated as part of a field value and `|' becomes the field
50           separator. Doing this may be useful in conjunction with a system
51           that wants to use pam_access with X based applications, since the
52           PAM_TTY item is likely to be of the form "hostname:0" which
53           includes a `:' character in its value. But you should not need
54           this.
55
56       listsep=separators
57           This option modifies the list separator character that pam_access
58           will recognize when parsing the access configuration file. For
59           example: listsep=, will cause the default ` ' (space) and `\t'
60           (tab) characters to be treated as part of a list element value and
61           `,' becomes the only list element separator. Doing this may be
62           useful on a system with group information obtained from a Windows
63           domain, where the default built-in groups "Domain Users", "Domain
64           Admins" contain a space.
65
66       nodefgroup
67           User tokens which are not enclosed in parentheses will not be
68           matched against the group database. The backwards compatible
69           default is to try the group database match even for tokens not
70           enclosed in parentheses.
71

MODULE TYPES PROVIDED

73       All module types (auth, account, password and session) are provided.
74

RETURN VALUES

76       PAM_SUCCESS
77           Access was granted.
78
79       PAM_PERM_DENIED
80           Access was not granted.
81
82       PAM_IGNORE
83           pam_setcred was called which does nothing.
84
85       PAM_ABORT
86           Not all relevant data or options could be gotten.
87
88       PAM_USER_UNKNOWN
89           The user is not known to the system.
90

FILES

92       /etc/security/access.conf
93           Default configuration file
94

SEE ALSO

96       access.conf(5), pam.d(5), pam(8).
97

AUTHORS

99       The logdaemon style login access control scheme was designed and
100       implemented by Wietse Venema. The pam_access PAM module was developed
101       by Alexei Nogin <alexei@nogin.dnttm.ru>. The IPv6 support and the
102       network(address) / netmask feature was developed and provided by Mike
103       Becher <mike.becher@lrz-muenchen.de>.
104
105
106
107Linux-PAM Manual                  06/08/2020                     PAM_ACCESS(8)
Impressum