Follow
#AskFedi: in a QUIC (*not* HTTP/3!) connection, how would one typically validate the key/identity of the other peer, when CA certificates are not available?
I'm looking at some QUIC implementations, and having trouble finding what I'd usually use; something like a client certificate fingerprint.
@joepie91 my (very possibly incomplete) understanding in that this is really a TLS question. I don't think QUIC add any additional identity mechanisms on topof what TLS already provides.