chiark / gitweb /
~ianmdlvl / elogind.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e2daa07) | patch
pam: include pam_keyinit.so in our PAM fragments
authorLennart Poettering <lennart@poettering.net>
Wed, 7 Dec 2016 19:14:43 +0000 (20:14 +0100)
committerSven Eden <yamakuzure@gmx.net>
Mon, 17 Jul 2017 15:58:35 +0000 (17:58 +0200)
commit8622c1b84e198fb2d0626e622dfeaaa446e38f3a
treee8196c3155c09f2bc5a46154ad8594db122e0ea8tree | snapshot
parente2daa07ca52e0dddb1a9f40b1c8fc9bab4e619b2commit | diff
pam: include pam_keyinit.so in our PAM fragments

We want that elogind --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 elogind --system sets up for us.
src/login/elogind-user.m4 diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.