aboutsummaryrefslogtreecommitdiff
path: root/cmd/fscrypt/status.go
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2020-01-29 19:27:10 -0800
committerGitHub <noreply@github.com>2020-01-29 19:27:10 -0800
commitc4fa1f4ccb407f44dfabf91d1214f06c277a1b9f (patch)
tree1711ccb6829abcf03a6874878d4fbd1709865e1e /cmd/fscrypt/status.go
parent0f06c53388f8b020e1a0d48af2f5e334c4ec2aca (diff)
cmd/fscrypt/commands: allow disabling recovery passphrase (#193)
While it's important to generate a recovery passphrase in the linked protector case to avoid data loss if the system is reinstalled, some people really don't want it (even though it can be safely ignored as it almost certainly has far more entropy than the login passphrase). As a compromise, prompt for y/n before generating it, with default y. Also, to allow disabling the recovery passphrase during noninteractive use, add a --no-recovery command-line option. Update https://github.com/google/fscrypt/issues/186
Diffstat (limited to 'cmd/fscrypt/status.go')
0 files changed, 0 insertions, 0 deletions