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.

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

cmd/fscrypt/commands: allow disabling recovery passphrase #193

Merged
merged 1 commit into from
Jan 30, 2020
Merged

cmd/fscrypt/commands: allow disabling recovery passphrase #193

merged 1 commit into from
Jan 30, 2020

Conversation

ebiggers
Copy link
Collaborator

@ebiggers ebiggers commented Jan 28, 2020

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 #186

@ebiggers
Copy link
Collaborator Author

Due to a merge conflict, this is based on #192.

Copy link
Member

@josephlr josephlr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this change, LGTM for 79720a0

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 #186
@ebiggers ebiggers merged commit c4fa1f4 into google:master Jan 30, 2020
@ebiggers ebiggers deleted the disable-recovery branch January 30, 2020 03:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants