tion is made with central configuration files and all changes are automatically inherited
by the PAM configuration of each service.
The first include file (
common-auth
) calls two modules of the
auth
type:
pam_env.so
and
pam_unix2.so
. See
Example 2.2, “Default Configuration for
the auth Section”
(page 21).
Example 2.2
Default Configuration for the auth Section
auth
required
pam_env.so
auth
required
pam_unix2.so
The first one,
pam_env
, loads the file
/etc/security/pam_env.conf
to set
the environment variables as specified in this file. This can be used to set the
DISPLAY
variable to the correct value, because the
pam_env
module knows about the location
from which the login is taking place. The second one,
pam_unix2
, checks the user's
login and password against
/etc/passwd
and
/etc/shadow
.
The whole stack of
auth
modules is processed before sshd gets any feedback about
whether the login has succeeded. Given that all modules of the stack have the
required
control flag, they must all be processed successfully before sshd receives
a message about the positive result. If one of the modules is not successful, the entire
module stack is still processed and only then is sshd notified about the negative result.
As soon as all modules of the
auth
type have been successfully processed, another
include statement is processed, in this case, that in
Example 2.3, “Default Configuration
for the account Section”
(page 21).
common-account
contains just one module,
pam_unix2
. If
pam_unix2
returns the result that the user exists, sshd receives a
message announcing this success and the next stack of modules (
password
) is pro-
cessed, shown in
Example 2.4, “Default Configuration for the password Section”
(page 21).
Example 2.3
Default Configuration for the account Section
account required
pam_unix2.so
Example 2.4
Default Configuration for the password Section
password requisite
pam_pwcheck.so
nullok cracklib
password required
pam_unix2.so
nullok use_authtok
Authentication with PAM
21
Summary of Contents for LINUX ENTERPRISE DESKTOP 11
Page 1: ...SUSE Linux Enterprise Server www novell com 11 March 17 2009 Security Guide...
Page 9: ...32 7 Managing Audit Event Records Using Keys 433 33 Useful Resources 435...
Page 10: ......
Page 29: ...Part I Authentication...
Page 30: ......
Page 55: ...Figure 4 2 YaST LDAP Server Configuration LDAP A Directory Service 41...
Page 126: ......
Page 127: ...Part II Local Security...
Page 128: ......
Page 158: ......
Page 173: ...Part III Network Security...
Page 174: ......
Page 194: ......
Page 197: ...Figure 16 2 Scenario 2 Figure 16 3 Scenario 3 Configuring VPN Server 183...
Page 210: ......
Page 228: ......
Page 229: ...Part IV Confining Privileges with Novell AppArmor...
Page 230: ......
Page 274: ......
Page 300: ......
Page 328: ......
Page 340: ......
Page 342: ......
Page 386: ......
Page 387: ...Part V The Linux Audit Framework...
Page 388: ......