3 ms·
Does QUIC or your implementation of it support application control of keying or is it always based on x.509 certs and CAs? edit: the spec (https://tools.ietf.o
by fulafel 7y ago
Does QUIC or your implementation of it support application control of keying or is it always based on x.509 certs and CAs?
edit: the spec (https://tools.ietf.org/html/draft-ietf-quic-tls-27 https://tools.ietf.org/html/draft-ietf-quic-tls-27) seems agnostic on this. Also simple APIs especially in security are important, so supporting certs only is no flaw in my book, just curious about the edges of how the OS QUIC could be used in the future.
- tialaramex 7y agoQUIC outsources this part of the solution to TLS (specifically TLS 1.3) so you just need a way to meet your needs in TLS 1.3 and it'll work in QUIC
- dochtman 7y agoThough it has been discussed that future versions of QUIC might allow other authentication/encryption protocols. Noise would be an interesting candidate.
- fulafel 7y agoNote that TLS doesn't necessarily imply certs either. TSL-PSK, TLS-SRP, anon DH, etc.
- tialaramex 7y agoSure, but, it's important to caveat that QUIC requires specifically TLS 1.3 (or potentially subsequent versions in the future) and so features which require older TLS versions aren't useful. Pre-shared keys are a thing in TLS 1.3 though there are subtle differences you ought to be aware of before implementing, but as I understand it SRP is not (at time of writing) and neither is anonymity. It isn't possible to "just" take an extension to TLS 1.2 that altered the handshake mechanism and have it work in TLS 1.3 because the handshake is very different even though it was camouflaged so that rusted-in-place TLS 1.2 middleboxes think it's just TLS 1.2 and don't freak out.