summaryrefslogtreecommitdiff
path: root/data/pam-lfs
diff options
context:
space:
mode:
authorRay Strode <rstrode@redhat.com>2016-08-15 14:11:01 -0400
committerRay Strode <rstrode@redhat.com>2016-08-19 15:02:07 -0400
commit31ed6f2b3f1ab45ae07aad41c13a51ba91fd159d (patch)
tree7a3ada2efa60d90050f726943bb29160dbce7723 /data/pam-lfs
parent714b6af29b916ac7da0cdab6f83460574ed49cf2 (diff)
downloadgdm-31ed6f2b3f1ab45ae07aad41c13a51ba91fd159d.tar.gz
pam: grab cached password from systemd and pass it on
If the user has an encrypted disk then systemd will cache the password they type into the keyring. It makes sense to try to use this password for automatic login purposes first, since on single user machines, the sole user password is likely to match the disk password. Of course if it doesn't work we'll fall back to the old way of doing automatic login without a password (and then the user will have to manualy enter if they need to for gnome-keyring or whatever) https://bugzilla.gnome.org/show_bug.cgi?id=769950
Diffstat (limited to 'data/pam-lfs')
-rw-r--r--data/pam-lfs/gdm-autologin.pam3
1 files changed, 3 insertions, 0 deletions
diff --git a/data/pam-lfs/gdm-autologin.pam b/data/pam-lfs/gdm-autologin.pam
index 13ac13ac..953d47e6 100644
--- a/data/pam-lfs/gdm-autologin.pam
+++ b/data/pam-lfs/gdm-autologin.pam
@@ -4,6 +4,8 @@ auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_succeed_if.so uid >= 1000 quiet
+auth optional pam_gdm.so
+auth optional pam_gnome_keyring.so
auth required pam_permit.so
account include system-account
@@ -12,5 +14,6 @@ password include system-password
session optional pam_keyinit.so revoke
session required pam_limits.so
session include system-session
+session optional pam_gnome_keyring.so auto_start
# End /etc/pam.d/gdm-autologin