This repository has been archived by the owner on Jun 17, 2022. It is now read-only.
hkdf crypto functions #190
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In some upcoming work with Send, I will need to use HKDF to expand a smaller encryption key that is part of the URL to a larger encryption key needed for our AES encryption functions.
Today we have an implementation of HKDF-Expand in our crypto service, but it is rather specific.
This PR creates generic crypto functions for HKDF and HKDF-Expand (web-crypto and node implementation) so that they can be used for other general crypto operations that we may need. The PR also ports the existing HKDF-Expand function in crypto service to use these new generic functions.
As with all crypto functions, unit tests were written to verify the correct implementation.