HKDF and TLS1-PRF EVP_PKEY key exchange wrapper #96
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 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.
HKDF and TLS1-PRF were available in OpenSSL 1.1.1 through the EVP_PKEY API. OpenSSL 3 introduced the EVP_KDF API, but some callers may still be using the EVP_PKEY API for KDF and TLS1-PRF. We have previously relied on the default provider's key exchange wrapper for these KDFs, which exposes them to the EVP_PKEY API. If the default provider is not enabled, or the caller sets "fips=yes", then the KDFs are no longer available to EVP_PKEY.
This PR adds a similar wrapper in the SymCrypt provider. Only TLS1-PRF and HKDF are needed for existing callers using EVP_PKEY functions. All other KDFs were not supported in OpenSSL 1.1.1, and new applications using those KDFs should use the EVP_KDF API.