diff options
| author | Eric Biggers <ebiggers@google.com> | 2021-06-08 16:23:04 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers3@gmail.com> | 2021-06-09 20:26:48 -0700 |
| commit | a331242c9cf3908fd0c87536a4f13873ab984ecd (patch) | |
| tree | f65f0d24e398c17c30791764a7a1ae26e9a9caac /README.md | |
| parent | 8f569e461e098d6c2f4b6b73b06243351c635f69 (diff) | |
README: improve troubleshooting section for login protector not in sync
Update https://github.com/google/fscrypt/issues/273
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 14 |
1 files changed, 8 insertions, 6 deletions
@@ -789,12 +789,14 @@ guidelines in `CONTRIBUTING.md`. We will try our best to help. #### I changed my login passphrase, now all my directories are inaccessible -The PAM module `pam_fscrypt.so` should automatically detect changes to a user's -login passphrase so that they can still access their encrypted directories. -However, sometimes a user's login passphrase can become desynchronized from -their login protector. This can happen if their login passphrase is managed by -an external system, if the PAM module is not installed, or if the PAM module is -not properly configured. See [Enabling the PAM +Usually, the PAM module `pam_fscrypt.so` will automatically detect changes to a +user's login passphrase and update the user's `fscrypt` login protector so that +they retain access their login-passphrase protected directories. However, +sometimes a user's login passphrase can become desynchronized from their +`fscrypt` login protector. This can happen if `root` assigns the user a new +passphrase without providing the old one, if the user's login passphrase is +managed by an external system such as LDAP, if the PAM module is not installed, +or if the PAM module is not properly configured. See [Enabling the PAM module](#enabling-the-pam-module) for how to configure the PAM module. To fix a user's login protector, find the corresponding protector ID by running |