HN Simulatornew | past | comments | lists | submit | jamilbk's commentslogin

Azure communication services (ACS - transactional emails) also appears to be down. Quite amazing one thing can roll out and break so many Microsoft services at once.

Here's the NIST link: https://nvd.nist.gov/vuln/detail/cve-2026-98432

Here are my notes so far after digging into this with Claude + defensive access:

1. Not just an MPTCP thing - any received IPv4 packet with options creates the problematic conditions.

2. Also appears that using NetLabel/CIPSO (SELinux or Smack with a CIPSOV4 mapping) creates the same conditions that a packet with IP options would. If you're using these, it might mean that dropping IPv4 packets with IP options might not fully mitigate.

3. At least for our test VMs in Azure (accelerated networking) I wasn't able to get any IPv4 packets with options through, from three different US-based ISPs. Unfortunately Microsoft publishes no docs on whether the fabric drops this or not, so YMMV.

We're using a simple XDP program to mitigate until a patched kernel is available (thanks @tptacek for the idea):

https://github.com/jamilbk/drop-ipv4-opt


Claude suggested this nftables-ipopt config + systemd unit to survive reboot will also fix the issue. Can anyone comment whether this is early enough in the stack to also solve this?

  cat > /etc/nftables-ipopt.nft <<'EOF'
  table inet ipopt {
    chain pre {
      type filter hook prerouting priority raw - 10; policy accept;
      ip hdrlength != 5 counter drop
    }
  }
  EOF
Also couldn't get IPv4 packets with options through between Hetzner cloud servers (different networks), but it's no guarantee.



I came here to make a similar comment. It seems like TigerBeetle was built for exactly the type of transactional processing this post is about?


We just invested a good amount of time restructuring our docs for Diátaxis. It was helpful, but I wouldn't take it as gospel. The important thing to remember is that each piece of content should be one of the four types.

If you're embarking upon a refactoring / rewriting journey for your docs, the only advice I'd share is to actually read the website beginning to end before starting. Especially this page: https://diataxis.fr/complex-hierarchies/. The guide is (unsurprisingly) very well written, and it's easy to internalize the concepts because they're repeated often.


Ugh, I don't like that page and I have actually deleted it. It'll be gone soon.

There is a real problem there, and that page doesn't do a good enough job of dealing with it. I have something cooking that is much, much better.


Is there some way for me to be notified when you do? I don't see any RSS on your site.

The docs I have built up are at times too technical for users and not detailed enough for developers. I am not sure if it's a skill issue on my part for an individual piece of text, a skill issue on my part in applying the principles outlined by Diataxis, or a fault in the framework itself (or its self-documentation).



Please post some kind of visible change notification (and something here) when you do!


We're currently in the process of restructuring our documentation and I'd be very interested in an early draft of this, fully understanding that caveat emptor. Is it published anywhere currently?


It makes sense to me (I agree with it), but I also agree that it doesn't really deal with it. I look forward to whatever you're cooking!


So its now 404'ing?


> read the website beginning to end before starting

Huh. The “Start here” page says exactly the opposite. It's literally the first two sentences on the page:

> You don’t need to read everything on this website to make sense of Diátaxis, or to start using it in practice. In fact I recommend that you don’t.

So what makes you recommend reading it all first?


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: