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
The OpenSSL project posted a blog entry that they are open to supporting external QUIC implementations, using OpenSSL as a TLS provider (not to be confused with OpenSSL cryptographic providers):
As part of our work, we will end up with interfaces that allow other QUIC implementations (outside of OpenSSL) to be able to use the TLS stack within OpenSSL – however that is not the initial focus of the work.
This is good news, and means that there may be a point at which the QuicTLS project will no longer be necessary. I look forward to the day when I can tell users of QuicTLS to use OpenSSL instead. But in the meantime, we will continue to keep QuicTLS up-to-date with OpenSSL through the 1.1.1 and 3.0 releases lifespans. The 3.1 and subsequent OpenSSL releases will be evaluated when they are released to see if they need QuicTLS added to them.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The OpenSSL project posted a blog entry that they are open to supporting external QUIC implementations, using OpenSSL as a TLS provider (not to be confused with OpenSSL cryptographic providers):
This is good news, and means that there may be a point at which the QuicTLS project will no longer be necessary. I look forward to the day when I can tell users of QuicTLS to use OpenSSL instead. But in the meantime, we will continue to keep QuicTLS up-to-date with OpenSSL through the 1.1.1 and 3.0 releases lifespans. The 3.1 and subsequent OpenSSL releases will be evaluated when they are released to see if they need QuicTLS added to them.
Beta Was this translation helpful? Give feedback.
All reactions