Top all-time · #8595
bert hubert
Personal blog · blog.netherlabs.nlsystemssecurity
bert hubert's personal blog at blog.netherlabs.nl covers systems and security. Since 2013, 9 different Hacker News readers have linked it 10 times, most often “Why is my tcp not reliable? (2009)”. The last post was in 2009, but the archive is still widely read.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link bert hubert's netherlabs posts as references on TCP shutdown and half-close behaviour, TCP reliability, and a 2008 post linked in a dnsmasq cache poisoning thread. Comments cite them rather than judge them.
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.
Most-linked posts?
- Why is my tcp not reliable? (2009)5 people · 6 mentions · first linked 2017-03-29
What Hacker News says?
shutdown() and half-closes are not "archaic" features. You need them to get even the basic stuff right (see https://blog.netherlabs.nl/articles/2009/01/18/the-ultimate-... ) and you need it even more to implement "modern" application layer protocols like HTTP2 (if you don't use it, you get data loss bugs like this: https://trac.nginx.org/nginx/ticket/1250#comment:4 ).
Comment linking /articles/2009/01/18/the-ultimate-so_linger-page-or-why-is-my-tcp-not-reliable
on “TCP is an underspecified two-node consensus algorithm”Submitted Why is my tcp not reliable? (2009) as a story · 131 points
HN discussionWow this brings up memories. I was at OpenDNS when Dan gave us the heads up. I'll just leave this here: https://blog.netherlabs.nl/articles/2008/07/09/some-thoughts...
Comment linking /articles/2008/07/09/some-thoughts-on-the-recent-dns-vulnerability
on “Critical Cache Poisoning Vulnerability in Dnsmasq”Submitted The SO_LINGER page, or: why is my TCP not reliable (2009) as a story · 68 points
HN discussion// it doesn't seem to love piping or redirecting output without this, even // with the newlines above fflush(stdout); Ah, the full buffering mode. I believe it can be fixed by calling setvbuf(stdout, NULL, _IOLBF, BUFSIZ); once at the start. On the whole, it actually almost implements the minimally required amount of HTTP/1.1: I would suggest adding support for HEAD requests, it's just a single flag that you need to…
Comment linking /articles/2009/01/18/the-ultimate-so_linger-page-or-why-is-my-tcp-not-reliable
on “Show HN: unsafehttp – tiny web server from scratch in C, running on an orange pi”Submitted The fourteen stages of any real software project – bert hubert (2008) as a story · 3 points
HN discussionNote that he links to http://blog.netherlabs.nl/articles/2009/01/18/the-ultimate-s... which more or less explains what's going on.
Comment linking /articles/2009/01/18/the-ultimate-so_linger-page-or-why-is-my-tcp-not-reliable
on “TCP is UNreliable”Submitted The Perfect Error Message as a story · 2 points
HN discussionSubmitted Why is my tcp not reliable? (2009) as a story · 2 points
HN discussionSubmitted Why is my TCP not reliable as a story · 1 points
HN discussion
