feat(blake3): add key derivation#73
Open
TamaraFinogina wants to merge 1 commit intoDaninet:masterfrom
Open
Conversation
Author
|
@Daninet, What do you think? |
Owner
|
I like the idea. Thank you for the PR. |
7 tasks
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
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.
PR for Discussion #72.
By design, Blake3 provides a key derivation mode that accepts a context string of any length and key material of any length, producing a derived key of any length. See Blake3 repo.
Hash-wasm didn't have it, but it's easy to add.
P.S. Test vectors are generated by the BLAKE3 team.