Add support for exporting keying material #729
+43
−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
Adds ssl_export_keying_material function to both pingora-openssl and pingora-boringssl ext modules. This wraps the underlying SSL library's export_keying_material method for RFC 5705 compliance.
This was referenced Nov 9, 2025
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.
Fixes #728
Adds
ssl_export_keying_materialfunction to bothpingora-opensslandpingora-boringsslext modules.This wraps the underlying SSL library's
export_keying_materialmethod for RFC 5705 compliance, enabling applications to derive keying material from established TLS connections for use cases like token binding and channel binding.The implementation provides a unified interface across both SSL backends.