diff options
| author | Eric Biggers <ebiggers@google.com> | 2020-01-27 19:24:30 -0800 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2020-01-27 19:24:30 -0800 |
| commit | d5b8bdcfba528c0c0e9f8052a705e454b26cb28f (patch) | |
| tree | 01e13351a05cb91154a52da3799be11821d61b9d /util/errors.go | |
| parent | 45c27d59ee40f3945837ea827f29f6896414157f (diff) | |
actions/recovery: ensure recovery passphrase is really custom_passphrase
If the login protector was just created by the same 'fscrypt encrypt'
command, then policy.Context.Config.Source will be pam_passphrase. This
needs to be overridden to custom_passphrase when creating the protector
for the recovery passphrase.
This fixes the following error:
fscrypt encrypt: login protectors do not need a name
Resolves https://github.com/google/fscrypt/issues/187
Update https://github.com/google/fscrypt/issues/186
Diffstat (limited to 'util/errors.go')
0 files changed, 0 insertions, 0 deletions