Skip to content

Commit

Permalink
pam: include pam_keyinit.so in our PAM fragments
Browse files Browse the repository at this point in the history
We want that systemd --user gets its own keyring as usual, even if the
barebones PAM snippet we ship upstream is used. If we don't do this we get the
basic keyring systemd --system sets up for us.
  • Loading branch information
poettering committed Dec 13, 2016
1 parent b3415f5 commit ab79099
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/login/systemd-user.m4
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,10 @@
# Used by systemd --user instances.

account required pam_unix.so

m4_ifdef(`HAVE_SELINUX',
session required pam_selinux.so close
session required pam_selinux.so nottys open
session required pam_selinux.so close
session required pam_selinux.so nottys open
)m4_dnl
session required pam_loginuid.so
session required pam_loginuid.so
session optional pam_keyinit.so force revoke
session optional pam_systemd.so

0 comments on commit ab79099

Please sign in to comment.