Explicitly allow unencrypted disclosures for alpha releases #2127
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
teor2345
added
A-docs
mpguerra
approved these changes
May 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We decided to skip generating and securing encryption keys until Zebra's first stable release.
But the policy we reference requires PGP encrypted emails, so we need to explicitly allow unencrypted disclosures for Zebra alpha releases.
Solution
Explicitly allow unencrypted disclosures for Zebra alpha releases.
Review
@dconnolly should review this update, it's not urgent.
Follow Up Work
Getting people in the habit of sending unencrypted disclosures might lead to accidental insecure disclosures. So we should make generating PGP keys a higher priority (#1638).