Fix missing encrypted key after emergency access reject #2078
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
Rejecting an emergency access request should transition the grantor/grantee relationship back into the `Confirmed` state, and the grantor's encrypted key should remain in escrow rather than being cleared, or else future emergency access requsts from that grantee will fail.
BlackDex
approved these changes
Oct 31, 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.
Rejecting an emergency access request should transition the grantor/grantee
relationship back into the
Confirmedstate, and the grantor's encrypted keyshould remain in escrow rather than being cleared, or else future emergency
access requsts from that grantee will fail.
This probably fixes #2061.