Asymmetric encryption support for EncString #222
Closed
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
|
No New Or Fixed Issues Found |
|
Replaced by #448 |
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.
Type of change
Objective
EncString now has a generic type param to indicate whether it's using Symm/Asymm encryption.
EncStringis now the equivalent ofBaseEncString<SymmetricKey>andAsymmetricEncStringisBaseEncString<AsymmetricKey>.Note that both
EncStringandAsymmetricEncStringare specific versions of theBaseEncString, which mean they both contain all the 7 variants we support, this is just to avoid code duplication while implementing parsing, but some of that might be able to be moved to the generic type.