You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rustls supports QUIC (now published as an RFC). OpenSSL still does not have QUIC support upstream. It would be nice if we exposed QUIC support in the bindings.
There's been interest in curl to support HTTP/3 with the rustls-ffi backend. It seems like one potential path towards that is to implement rustls-ffi as a TLS provider choice in ngtcp2.
I'd like to use this issue to track the general goal of supporting QUIC projects using rustls-ffi, with ngtcp2 as a first target. I think the most immediate next steps are to:
Identify and understand the TLS API integration points in ngtcp2, and confirm they can be mapped to the Rustls-native QUIC API.
Expose the required Rustls-native types/APIs in rustls-ffi (e.g. items from the 0.23 quic module)
Implement ngtcp2 support to use rustls-ffi as a TLS provider
If necessary, implement the glue in curl for ngtcp2+rustls-ffi support for HTTP/3
As a general disclaimer, I'd like to make progress here but have to approach it during my spare time as interest strikes unless there's a sponsor interested in accelerating the work with financial backing.
Activity
cpu commentedon Feb 25, 2026
There's been interest in curl to support HTTP/3 with the rustls-ffi backend. It seems like one potential path towards that is to implement
rustls-ffias a TLS provider choice in ngtcp2.I'd like to use this issue to track the general goal of supporting QUIC projects using rustls-ffi, with ngtcp2 as a first target. I think the most immediate next steps are to:
quicmodule)As a general disclaimer, I'd like to make progress here but have to approach it during my spare time as interest strikes unless there's a sponsor interested in accelerating the work with financial backing.