-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access to low-level quinn::Connection
#154
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I need access to
peer_identity
andhandshake_data
, andexport_keying_material
fns of thequinn::Connection
to run some security assertions in the WebTransport handler, but I figured this low-level access could simpler be provided by exposing the wholequinn::Connection
with the corresponding feature-flag enabled.To provide some additional context: we want to tie the transport security to an AMD SEV-SNP attestation report.
See AMD SEV SNP spec for more info.
For that, we'd want to use key material exports and pass them into the attestation reports alongside our own nonces.
The WebTransport-specific spec for this is still underway, but we can already use it at the QUIC level via
quinn
implementation.You might want to implement WebTransport TLS Keying Material Exporter at
wtransport
too - I created #155.The text was updated successfully, but these errors were encountered: