aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2021-03-08 15:20:08 -0800
committerEric Biggers <ebiggers@google.com>2021-03-08 15:20:08 -0800
commitb7e898f01bcae17174fcd928599d0d933655db9b (patch)
treea53f09298957ead959a360cb1af0ba9460e8ce9e /README.md
parent28e4999ebd9221a71488d715d9f1182b494216d8 (diff)
pam_fscrypt: make "lock_policies" the default behavior
All pam_fscrypt configuration guides that I'm aware of say to use the "lock_policies" option for the pam_fscrypt.so session hook. The Debian/Ubuntu pam-config-framework config file has it too. Make locking the default behavior, since this is what everyone wants. Existing configuration files that contain the "lock_policies" option will continue to work, but that option won't do anything anymore. (We could add an option "unlock_only" to restore the old default behavior, but it's not clear that it would be useful. So for simplicity, leave it out for now.)
Diffstat (limited to 'README.md')
-rw-r--r--README.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.md b/README.md
index 4a59535..97caed2 100644
--- a/README.md
+++ b/README.md
@@ -415,12 +415,12 @@ auth optional pam_fscrypt.so
after `pam_unix.so` in `/etc/pam.d/common-auth` or similar, and to add the
line:
```
-session optional pam_fscrypt.so lock_policies
+session optional pam_fscrypt.so
```
-after `pam_unix.so` in `/etc/pam.d/common-session` or similar. The
-`lock_policies` option locks the directories protected with the user's login
-passphrase when the last session ends. All the types also support the `debug`
-option which prints additional debug information to the syslog.
+after `pam_unix.so` in `/etc/pam.d/common-session` or similar.
+
+To make `pam_fscrypt.so` print debugging messages to the system log, add the
+`debug` option. All hook types accept this option.
### Allowing `fscrypt` to check your login passphrase