47 karma · joined August 1, 2025
1. That for this to be a DOS type exploit, the attacker needs to exploit a race condition over network, which is an incredibly unlikely event that one can't really force.
2. For it to be a root exploit they need to craft the IP options with a specific memory address, but that memory address isn't known to the attacker because it's not a constant (see KASLR).
3. There is also a simple fix by simply adjusting iptables, and much/most/many network setups already drop IP options by default.
If I'm misunderstanding something let me know, but in practice this doesn't seem like it's likely to cause much damage. The people at Canonical and Redhat probably came to same conclusions and are balancing the true risk (not CVE risk level which are not very useful) with the potential for introducing a regression for their customers. This kind of stuff happens somewhat often and never catches fire like this, I think Anthropic is just fanning the flames and Ubuntu is taking the heat.
Not accepting cash is probably more to do with not wanting to deal with it, not needing to trust employees with it, keeping poor people out, and preventing robbery.
Credit card companies and banks know basically squat about your purchase except in certain circumstances (buying gas or flights causes more data to follow, called L2 or L3 data), or if they work with a data enrichment provider. There is a lot of action in this space right now, but the banks are hardly equipped to handle more data even if it became available.
I guess it makes sense though, unless you've got the lowest pricing on your own model how can you compete.
Which is why I think we need to be less critical everytime Mozilla tries to make money some other way. They need to become more self sufficient in order to improve Firefox.
It's also easy to accidentally make your DB queries sequentially or lazily. Using select_related is critical.
Not to mention that film rolls do wear out overtime.