Add Argon2 (RFC 9106) to Cryptography Registry #793
+15
−0
Conversation
This file contains hidden or 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
Add Argon2 (RFC 9106) to the Cryptography Registry with a parameterized pattern aligned to RFC terminology.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds Argon2 (RFC 9106) to
schema/cryptography-defs.json.Notes on parameter naming vs Issue #756
Issue #756 proposes:
Argon2(id|i|d)[-{memoryMiB}][-{iterations}][-{parallelism}].RFC 9106 defines:
mas memory size in kibibytes (KiB),tas number of passes,pas degree of parallelism.Accordingly, this PR uses:
Argon2(id|i|d)[-{memoryKiB}][-{passes}][-{parallelism}]If the community prefers the Issue's naming for consistency with existing conventions, I can update the pattern accordingly.
Refs: #756