feat(s2n-quic-transport): support exporting from TLS sessions #1984
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.
Description of changes:
This adds support for exporting symmetric keys from the negotiated QUIC connection for use by other applications/protocols. See https://datatracker.ietf.org/doc/html/rfc5705 for some further details.
See s2n-tls upstream (aws/s2n-tls#4230), released as part of s2n-tls 0.0.39 on crate.io. rustls already supports the relevant API.
Call-outs:
The event API is somewhat novel as added here, but should be relatively extensible and works out ok.
Testing:
New test added.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.