07e5e43489
Modified pam-config package to add support to Debian packaging. Test Plan: PASS: Package installed and ISO built sucessfully PASS: Package files were copied with right permissions Story: 2009256 Task: 43544 Signed-off-by: Yan Kabuki <Yan.HiroakiKabuki@windriver.com> Change-Id: I1bc1704f795a9ca477aee479c83074bbbdf10a42
28 lines
1.4 KiB
Plaintext
Executable File
28 lines
1.4 KiB
Plaintext
Executable File
#
|
|
# /etc/pam.d/common-account - authorization settings common to all services
|
|
#
|
|
# This file is included from other service-specific PAM config files,
|
|
# and should contain a list of the authorization modules that define
|
|
# the central access policy for use on the system. The default is to
|
|
# only deny service to users whose accounts are expired in /etc/shadow.
|
|
#
|
|
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
|
|
# To take advantage of this, it is recommended that you configure any
|
|
# local modules either before or after the default block, and use
|
|
# pam-auth-update to manage selection of other modules. See
|
|
# pam-auth-update(8) for details.
|
|
#
|
|
|
|
# here are the per-package modules (the "Primary" block)
|
|
account required pam_faillock.so
|
|
account [success=2 new_authtok_reqd=done default=ignore] pam_unix.so
|
|
account [success=1 new_authtok_reqd=done default=ignore] pam_ldap.so
|
|
# here's the fallback if no module succeeds
|
|
account requisite pam_deny.so
|
|
# prime the stack with a positive return value if there isn't one already;
|
|
# this avoids us returning an error just because nothing sets a success code
|
|
# since the modules above will each just jump around
|
|
account required pam_permit.so
|
|
# and here are more per-package modules (the "Additional" block)
|
|
# end of pam-auth-update config
|