diff options
| author | Robert McQueen <rob@endlessos.org> | 2021-03-03 11:34:55 +0000 |
|---|---|---|
| committer | Eric Biggers <ebiggers3@gmail.com> | 2021-03-03 10:06:13 -0800 |
| commit | 90a96e4473ae7bcf61a97f25fc67a9a953187f56 (patch) | |
| tree | 792a05deb13396c26b95ac7e94cac5c660c66f98 /metadata/checks.go | |
| parent | 7fa623a0c9fe043ab709e48f43d1fc44f51f5f5a (diff) | |
pam_fscrypt/config: prioritise over other session modules
Services launched by systemd user sessions on Debian / Ubuntu systems
are often not able to access the home directory, because there is no
guarantee / requirement that pam_fscrypt is sequenced before
pam_systemd.
Although this pam-config mechanism is Debian-specific, the config file
is provided here upstream and unmodified in Debian. Raising the
priority here so that it's always ordered ahead of pam_systemd will
solve issues such as https://github.com/google/fscrypt/issues/270,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964951 and
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1889416.
After a survey of pam-config files available in Debian bullseye, the
value of 100 was chosen as it appears after most other plugins that
could be involved in more explicit homedir configuration (eg pam_mount
at 128) but before those which seem unlikely to work without a home
directory (eg pam_ssh at 64).
Diffstat (limited to 'metadata/checks.go')
0 files changed, 0 insertions, 0 deletions