Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README: document issue with ssh ChallengeResponseAuthentication #329

Merged
merged 1 commit into from
Dec 20, 2021
Merged

README: document issue with ssh ChallengeResponseAuthentication #329

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 21 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -916,13 +916,27 @@ First, directories won't unlock if your session starts without password
authentication. The most common case of this is public-key ssh login. To
trigger a password authentication event, run `su $USER -c exit`.

If your session did start with password authentication, then either the PAM
module is not correctly installed and configured, or your login passphrase
changed and got out of sync with your login protector. Ensure you have
correctly [configured the PAM module](#enabling-the-pam-module). Then, if
necessary, [manually change your login protector's
passphrase](#i-changed-my-login-passphrase-now-all-my-directories-are-inaccessible)
to get it back in sync with your actual login passphrase.
If your session did start with password authentication, then the following may
be causing the issue:

* The PAM module might not be configured correctly. Ensure you have correctly
[configured the PAM module](#enabling-the-pam-module).

* If your login passphrase recently changed, then it might have gotten out of
sync with your login protector. To fix this, [manually change your login
protector's
passphrase](#i-changed-my-login-passphrase-now-all-my-directories-are-inaccessible)
to get it back in sync with your actual login passphrase.

* Due to a [bug in sshd](https://bugzilla.mindrot.org/show_bug.cgi?id=2548),
encrypted directories won't auto-unlock when logging in with ssh using the
`ChallengeResponseAuthentication` ssh authentication method, which is also
called `KbdInteractiveAuthentication`. This ssh authentication method
implements password authentication by default, so it might appear similar to
`PasswordAuthentication`. However, only `PasswordAuthentication` works with
`fscrypt`. To avoid this issue, make sure that your `/etc/ssh/sshd_config`
file contains `PasswordAuthentication yes`, `UsePAM yes`, and either
`ChallengeResponseAuthentication no` or `KbdInteractiveAuthentication no`.

#### Getting "encryption not enabled" on an ext4 filesystem

Expand Down