Support multiple keyAgreement keys #166
Merged
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
…ld be encrypted for both of them, ensuring that all keyholders can decrypt.
|
This matches the behavior described in the DIDComm Spec for message encryption: https://identity.foundation/didcomm-messaging/spec/#did-document-keys. Therefore I vote to accept this PR. It should be fully backwards compatible from what I can see. |
mirceanis
approved these changes
May 11, 2021
uport-automation-bot
pushed a commit
that referenced
this pull request
May 11, 2021
# [5.3.0](5.2.0...5.3.0) (2021-05-11) ### Features * use multiple keyAgreementKeys when creating JWE ([#166](#166)) ([e327ef2](e327ef2))
|
🎉 This PR is included in version 5.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
If a DID contains more than one valid keyAgreement key, payloads should be encrypted for both of them, ensuring that all keyholders can decrypt.