At least if you’re on Amazon Web Services behind a load balancer you probably aren’t really that impacted enough to spend Halloween patching.

> AWS Web Application Firewall, Application Load Balancer, Classic Load Balancer, TLS Listeners on Network Load Balancer, Cloud Front, API Gateway

> Customers using the above services do not receive TCP connections from untrusted sources directly when following best practices. AWS is applying updates to the underlying infrastructure of these services and no immediate customer action is required if you are using these services. We still recommend customers update their self-managed instances behind these services within the next 30 days.

[0]: https://aws.amazon.com/security/security-bulletins/2026-160-...

▲

gwbas1c 2 hours ago | parent | next [-]

I'm more worried about my consumer-grade router.

	▲	wtch98 2 hours ago \| parent [-]
		I blocked packets arriving externally on my firewall with ip-options a couple of days ago. Firewall rule has zero hits, and I've got a very open ISP (andrews+arnold), if I want I can host SMTP, DNS, whatever

▲

lysace 9 minutes ago | parent | prev | next [-]

Note: AWS NLB doesn't terminate TCP on TCP listeners.

▲

sebmellen 2 hours ago | parent | prev [-]

Another reason hyperscaler cloud providers will continue to grow (IMO)!

	▲	TuxPowered 10 minutes ago \| parent \| next [-]
		My FreeBSD loadbalancers block packets with IP Options with default config. It’s not rocket science, no matter how Cloud providers are trying to tell us.
	▲	exyi 36 minutes ago \| parent \| prev [-]
		My VPS was auto-updated and restarted more than 14 days ago. The logs have rolled already. Probably October 12 early morning. Another reason NixOS will continue to grow :)