News for hackers. Stuff that matters.
Re:Why HTTP/3 is eating the world by treesknees on Thursday October 05, 2023 @12:43PM (#37780844)
It's an implementation limit that at least Chrome (and possibly other browsers) are enforcing for QUIC connections. The TLS certificate must be signed by a trusted CA. [1]

There does appear to be cli flags to change the behavior, but I don't see how you'd do that on mobile or embedded browsers.

[1]https://www.smashingmagazine.com/2021/09/http3-practical-dep...

Re:Why HTTP/3 is eating the world by remram on Thursday October 05, 2023 @01:33PM (#37781446)
You can add trusted CAs to your system though...
Re:Why HTTP/3 is eating the world by treesknees on Thursday October 05, 2023 @11:13PM (#37786788)
That is true. But an actual self-signed certificate is not signed by any CA, so it still can't be used with QUIC connections (with specific clients such as Chrome, anyway.)