Update TLS 1.3 KDF to use proper wolfcrypt FIPS APIs #352
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
padelsbach
reviewed
Jan 21, 2026
padelsbach
approved these changes
Jan 21, 2026
ColtonWilley
force-pushed
the
wp_tls13_kdf_fips
branch
from
e8145ca to
3383fc7
Compare
Contributor
Author
|
jenkins retest this please |
kaleb-himes
approved these changes
Jan 26, 2026
Contributor
kaleb-himes
left a comment
kaleb-himes
left a comment
There was a problem hiding this comment.
Thanks @ColtonWilley these changes look great.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Update TLS 1.3 KDF to use proper wolfcrypt FIPS APIs