Items tagged with: openssl

Search

Items tagged with: openssl

I'll talk #http3 again this week and I made this new slide explaining the #OpenSSL #QUIC "journey"

Did I miss any major milestone I should add?

The OpenSSL QUIC path from cirka 2019 until today
#http3 #OpenSSL #quic

#OpenSSL

#OpenSSL #quic #curl

An #ngtcp2 lead developer told me they have no current plans to adapt to the new #OpenSSL #QUIC API because of its lack of 0RTT support and the "pull model".

Of course someone else can go ahead and write it and ideally someone from #OpenSSL does it, for dogfooding purposes.

I have no heard of any other QUIC stack either having adapted to it yet.

#OpenSSL #quic #ngtcp2

I asked the #OpenSSL team about their new #QUIC API:

Out of curiosity: since you decided to provide a quite different API than what was once offered to you and what several QUIC stacks are already using. How did you come up with this API?

github.com/openssl/openssl/pul…


Add an API for other QUIC stacks to use our TLS implementation by mattcaswell · Pull Request #26683 · openssl/openssl

We provide some callbacks for third party QUIC stacks to use in order to be able to reuse the OpenSSL TLS implementation in that stack. This is essentially a thin wrapper around the same API that O...
GitHub
#OpenSSL #quic

I now hope for #OpenSSL to work with #ngtcp2 to make sure #QUIC works fine in that combo. Then we can leave the slow OpenSSL-QUIC implementation in its dusty corner and perhaps see rather wide HTTP/3 + curl adoption coming up.
#OpenSSL #quic #ngtcp2

I wonder if #MsQuic will then switch back to #OpenSSL again once 3.5 is released 🤔 (or at least allow the usage of #OpenSSL in addition to #quictls 😅)
#OpenSSL #quictls #msquic

#OpenSSL #quic

Until improved, I believe the sever performance degradation and memory use compared to #ngtcp2 are reasons enough for us to not recommend #OpenSSL QUIC for use with #curl in production.

Upload speed: ngtcp2 is 2-4x faster.

Memory use: in some tests, OpenSSL uses 25x the amount of memory.

#OpenSSL #curl #ngtcp2

Three years ago I blogged about #OpenSSL's decision to deliberately block #QUIC progress in the world: daniel.haxx.se/blog/2021/10/25…

Which is timely with the OpenSSL 3.4.0 release announced just days ago: that still does not offer a working (and performant) QUIC API. (yes, there is an attempt there but it's not production grade)

It's almost like the writing was on the wall already a long time ago.

The QUIC API OpenSSL will not provide

In a world that is now gradually adopting HTTP/3 (which, as you know, is implemented over QUIC), the problem with the missing API for QUIC is still a key problem.
daniel.haxx.se
#OpenSSL #quic

#OpenSSL #haproxy

#OpenSSL #quic

According to @bagder the stubborn way the #OpenSSL project is handling #QUIC implementation is directly responsible for delaying HTTP/3 adoption (1), and I tend to agree. When the project rejected the community QUIC patches and decided to go with their own design, it wasn't difficult to predict problems. This was proven right by the massive feature gaps (2) and performance issues (3) discovered by @icing when trying to marry OpenSSL QUIC to #curl. Even with API fixes released in version 3.3 the implementation is still inferior, and there is no good solution in sight.

1) lwn.net/Articles/983380/
2) github.com/openssl/openssl/dis…
3) github.com/icing/blog/blob/mai…


blog/curl-h3-performance.md at main · icing/blog

Contribute to icing/blog development by creating an account on GitHub.
GitHub
#OpenSSL #quic #curl @daniel:// stenberg:// @Stefan Eissing

#lwn #OpenSSL

#OpenSSL #curl

#OpenSSL #curl #nghttp3

#OpenSSL #quic #curl

There are TLS servers that don't send the required close_notify alert message in certain conditions. #Google web servers do this if they think the that recipient isn't interested about the message body and no connection keep alive is set. Examples of such connections would be requests that end up with 0 byte message body while:
• HTTP/1.0 without "Connection: keep-alive" header or
• HTTP/1.1 with "Connection: close" header

This can cause some complications since #OpenSSL 3 defaults to erroring out if the close_notify is missing.

SSL_OP_IGNORE_UNEXPECTED_EOF option was added to enable talking to these non-compliant servers. Enabling this option removes truncation attack protection - so this option should really only be used when absolutely necessary. However, unless if you control the servers being talked to, you probably need to enable this option for now.

So why does Google terminate connections without close_notify? Likely it is done to save some resources when tearing down TLS connections. If you have billions of connections going on all the time, even some small savings add up quickly.

github.com/php/php-src/issues/…


OpenSSL 3: Support of SSL_OP_IGNORE_UNEXPECTED_EOF context option · Issue #8369 · php/php-src

Description OpenSSL became more strict about unexpected EOF (not sending close notify) in 1.1.1e but reverted that change in 1.1.1f due to the huge amount of non-compliant servers. With the new maj...
GitHub
#google #OpenSSL

#OpenSSL #quic #curl

We just created a #HOWTO for how to set up dev/test servers using our #TLS #EncryptedClientHello #ECH enabled forks of #OpenSSL #nginx and #curl running on #Debian. It should be very quick to get started using a new domain: guardianproject.info/2023/11/1…

Quick set up guide for Encrypted Client Hello (ECH)

The Encrypted Client Hello (ECH) mechanism draft-spec is a way to plug a few privacy-holes that remain in the Transport Layer Security (TLS) protocol that’s used as the security layer for the web.
jochensp (https://guardianproject.info)
#debian #tls #OpenSSL #howto #curl #ech #nginx #encryptedclienthello

I feel for you. I'm sure you are far from alone in such an unfortunate situation. I blame #OpenSSL for not caring much about their users.
#OpenSSL

#OpenSSL

#OpenSSL #quic

#OpenSSL

#OpenSSL @OCR Bot

⇧