4 ms·

With HTTP/3 there isn't much higher level packet analysis to do between anything useful in the headers being encrypted and the session being reused. All you see

With HTTP/3 there isn't much higher level packet analysis to do between anything useful in the headers being encrypted and the session being reused. All you see is there is a 443 UDP session to a Google server and encrypted packets keep getting sent back and forth... which looks exactly like any other HTTP/3 session to a Google server. I think the weak points are wholly untechnical e.g. Google would often give in to protect the $$$ they make in a region.

toast0 2y ago
Packet size (i forget if http/3 does padding) and packet rates are still available, dns looks a lot different than most http content.
- zarzavat 2y ago
  In terms of packet size, DNS (DoH) doesn’t really look any different to an XHR request.
  - toast0 2y ago
    Request maybe, DoH responses are probably way shorter than anything else though.