Alessandro Ghedini

@brbzull0 I was going to do it, just got delayed by travel. Thanks for your work, this is merged now!

Hey @qdeconinck, thanks for your continued work on this. We've been working on testing and integrating this into our stack, so I've now started looking into rebasing this (there's a...

Merged, thanks @bwoebi!

Sorry for the delay, this merged now, thanks @junhochoi!

I made https://github.com/cloudflare/quiche/pull/1615 which makes it possible to run some of the CI builds with different TLS features. Once that's merged you should be able to just add "openssl" to...

If I understand this correctly, I don't think there's anything we can do about this, as it's just a limitation with `cargo install`, see e.g. https://github.com/rust-lang/cargo/issues/2552

Yeah but we have no control over how `cargo install` works.

> And the handshake only completes once the HANDSHAKE_DONE frame (shown as DONE in the packet logs) has been sent. Nope, per [RFC9001, Section 4.1.1](https://datatracker.ietf.org/doc/html/rfc9001#name-handshake-complete): > In this document, the...

> This should be replaced with something robust, e.g. bindgen. Yes, though the main complication is that we don't enforce a specific version of BoringSSL and we don't necessarily have...

This will cause application close frames to be sent in Initial and Handshake packets, which is a violation of §12.5 of the transport draft: > CONNECTION_CLOSE frames signaling application errors...