[#11] - Bind Keys to Version and Purpose. #12
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
Adds strong key types for both V1 and V2: - SymmetricKey: Key for LOCAL tokens. - AsymmetricPublicKey: Public key for PUBLIC tokens. - AsymmetricSecretKey: Secret key for PUBLIC tokens. Byte arrays are no longer accepted and must be wrapped in these types with the correct version attached. Test vectors show usage, docs will be updated to reflect this and other v1.0 changes. More details can be found here and in issue #11: https://github.com/paseto-standard/paseto-spec/blob/master/docs/02-Implementation-Guide/03-Algorithm-Lucidity.md
paragonie-security
approved these changes
Aug 7, 2021
|
Thanks for taking a look and making the suggestion! I'm going to write some tests then merge this. |
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.
Adds strong key types for both V1 and V2:
Byte arrays are no longer accepted and must be wrapped in these types
with the correct version attached. Test vectors show usage, docs will
be updated to reflect this and other v1.0 changes.
More details can be found here and in issue #11:
https://github.com/paseto-standard/paseto-spec/blob/master/docs/02-Implementation-Guide/03-Algorithm-Lucidity.md