8000 cmd/fscrypt: adjust message when listing protector sources by ebiggers · Pull Request #166 · google/fscrypt · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

cmd/fscrypt: adjust message when listing protector sources #166

New issue
< 8000 div class="px-4">

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

Jump to bottom
Merged
merged 1 commit into from
Nov 27, 2019
Merged

cmd/fscrypt: adjust message when listing protector sources #166

merged 1 commit into from
Nov 27, 2019

Conversation

ebiggers
Copy link
Collaborator

Saying "Your data can be protected with one of the following sources" is
ambiguous because it could be interpreted to mean that an encrypted
directory can only have one type of protector. In fact, an encrypted
directory can have multiple protectors, and they can be of any type.

Update #164

@ebiggers ebiggers requested a review from josephlr November 27, 2019 01:24
@ebiggers
cmd/fscrypt: adjust message when listing protector sources
10bbfcb 
Saying "Your data can be protected with one of the following sources" is
ambiguous because it could be interpreted to mean that an encrypted
directory can only have one type of protector.  In fact, an encrypted
directory can have multiple protectors, and they can be of any type.

Update #164
7287
@ebiggers ebiggers merged commit 10bbfcb into google:master Nov 27, 2019
@ebiggers ebiggers deleted the protector-source-wording branch November 27, 2019 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@josephlr josephlr Awaiting requested review from josephlr

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ebiggers
0