google / fscrypt / 470

34%

push

travis-ci

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

9 of 9 new or added lines in 1 file covered. (100.0%)

1606 of 4815 relevant lines covered (33.35%)

1066.48 hits per line