summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarol Lewandowski <k.lewandowsk@samsung.com>2014-03-12 18:29:25 +0100
committerKarol Lewandowski <k.lewandowsk@samsung.com>2014-03-12 18:49:57 +0100
commitf879c183094dea0636c195bd96b96c2c00f32559 (patch)
tree834ca6beb3ab3485a38a7f763df22a179e918e7e
parentd2a097ba110167aeb4cfffe62042fb7119f27f30 (diff)
downloadpam-accepted/tizen_ivi_panda.tar.gz
pam-accepted/tizen_ivi_panda.tar.bz2
pam-accepted/tizen_ivi_panda.zip
Having pam_systemd.so enabled globally causes systemd --user to be spawned for every login. This is a problem at least for ssh, sdb and /bin/login (eg. serial console) logins. This commit drops pam_systemd from systemd-auth with expectation that it will be added in pam config for graphical login manager (or similar). Change-Id: I933f9391e7e7d45adb148567e41e1cd66de9986d Signed-off-by: Karol Lewandowski <k.lewandowsk@samsung.com>
-rw-r--r--packaging/system-auth1
1 files changed, 0 insertions, 1 deletions
diff --git a/packaging/system-auth b/packaging/system-auth
index 44a1011..4f8b4f0 100644
--- a/packaging/system-auth
+++ b/packaging/system-auth
@@ -11,7 +11,6 @@ password sufficient pam_unix.so try_first_pass nullok sha512 shadow
password required pam_deny.so
session optional pam_keyinit.so revoke
-session optional pam_systemd.so
session required pam_limits.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session required pam_unix.so