Once enterprise builds the systems and gets their revisions into every Blue Coat middlebox, half the engineering work of those abusive governments is done.
Yeah, I mean, more generally, one could/should analyze QUIC more generally to see if there are unnecessary covert channels. I assume that since it uses TLS 1.3 then Server.Random is still one, for example.
-
-
The harder problem with QUIC is that the server could just send out a junk QUIC record that the client throws away, which contains the)(encrypted) information for the MitM to process. So, probably there's not much one could do.
-
Ya quic is designed ignore things that don’t decrypt so you could technically send a malformed udp packet with anything in it
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.