Top all-time · #13091
Christian Huitema
Personal blog · huitema.wordpress.comsystemssecurity
Christian Huitema's personal blog at huitema.wordpress.com covers systems and security. Since 2018, 6 different Hacker News readers have linked it 6 times. The last post was in 2022, but the archive is still widely read.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
Commenters cite the blog as a source on encrypted SNI in TLS and as context in discussions of DNS and RFC authorship. The comments do not judge the writing itself.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Keeping working on this Internet thing...
Most-linked posts?
- /2017/09/12/cracking-the-sni-encryption-nut/2 people · 2 mentions · first linked 2018-06-26
What Hacker News says?
Something that nobody seems to be talking about here is the congestion control algorithm, which is the problem here. Cubic doesn't like losses. At all. In the kernel, pacing is implemented to minimise losses, allowing Cubic to work acceptably for TCP, but if the network is slightly lossy, the perfs are terrible anyway. QUIC strongly recommends to implement pacing but it's less easy to implement accurately in userlan…
Comment linking /2019/11/11/implementing-cubic-congestion-control-in-quic/
on “QUIC is not quick enough over fast internet”Submitted Pi-Hole vs. DNS Privacy as a story · 5 points
HN discussionThere are people working on encrypted SNI: https://huitema.wordpress.com/2017/09/12/cracking-the-sni-en... it'll take some time, but we'll get there hopefull soon.
Comment linking /2017/09/12/cracking-the-sni-encryption-nut/
on “Firefox’s Trusted Recursive Resolver DNS feature is dangerous”Submitted Having fun and surprises with IPv6 as a story · 4 points
HN discussionContext: https://huitema.wordpress.com/2017/09/12/cracking-the-sni-en...
Comment linking /2017/09/12/cracking-the-sni-encryption-nut/
on “Issues and requirements for SNI encryption in TLS”There was an A6 record type ( https://www.rfc-editor.org/rfc/rfc2874.txt ), but it was rejected ( https://www.rfc-editor.org/rfc/rfc3364.txt ) in favor of the original AAAA record type ( https://www.rfc-editor.org/rfc/rfc1886.txt ). Christian Huitema is listed as an author on both AAAA and A6 RFCs, so maybe they know why the AAAA identifier was originally chosen instead of A6. Unfortunately, Google doesn't provide a…
Comment linking /
on “DNS A and AAA records for Facebook, Instagram and WhatsApp have been destroyed”