b999d48941
We're losing the svn history (which we could probably keep if we tried hard enough) but don't consider that worthwhile. Note these tests are destructive, so run them only in a throwaway environment like a chroot, container, or vm. The tests/run.all script should be the one which launches all the tests. Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
#
|
|
# /etc/pam.d/common-session-noninteractive - session-related modules
|
|
# common to all non-interactive services
|
|
#
|
|
# This file is included from other service-specific PAM config files,
|
|
# and should contain a list of modules that define tasks to be performed
|
|
# at the start and end of all non-interactive sessions.
|
|
#
|
|
# 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)
|
|
session [default=1] pam_permit.so
|
|
# here's the fallback if no module succeeds
|
|
session 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
|
|
session required pam_permit.so
|
|
# and here are more per-package modules (the "Additional" block)
|
|
session required pam_unix.so
|
|
# end of pam-auth-update config
|