HTTP/2 & Quic - Teaching Good Protocols to Do Bad Things
summary
HTTP/2 adoption reaches roughly 15% of the Alexa top 1M and QUIC already appears on many Google properties and over a billion Chrome clients, while ~93% of networks allow outbound UDP on ports 80/443. The talk shows a working H1↔QUIC proxy tunnel that carries a reverse shell — it succeeds but interactive sessions are borderline unusable due to multiplexing and implementation limits. Wireshark mostly shows encrypted garbage; a tiny C-based QUIC detector (ntop-derived) finds packets; tools and code are slated for release.
AI-written summary · about
chapters (17)
- 0:00Welcome and introductions
- 1:24Speaker backgrounds
- 3:03Protocol teasers
- 5:04Need for new protocols
- 5:55Protocol impact
- 8:35TCP limitations
- 10:57Shift to HTTP/2 and QUIC
- 12:54Protocol evolution
- 14:33Current deployment statistics
- 17:30Multiplexing concepts
- 19:48HTTP/2 technical details
- 27:48QUIC technical details
- 32:20Exploiting new protocols
- 39:23Network security challenges
- 41:22Detection and defense
- 44:21Analysis tools
- 45:59Conclusions and Q&A
related talks
28mHTTP 2.0 and QUIC - protocols of the (near) future
40mHTTP/3 - HTTP over QUIC is the next generation
30mQUIC, in Theory and Practice
43mDeploying and Debugging HTTP/3
51mHTTP/3 and QUIC: Who, what, where, when and, WHY?
12mThe QUIC-ematic universe season 2020-2021 preview
01h 00mHTTP/2 - The future of the web today
34mQUIC and HTTP/3: Too Big to Fail?!