Comment by AdrianCX 15 hours ago so just block multipath and add the firewall rule from article that drops packets with IPv4 options 4 comments AdrianCX Reply stefangordon 14 hours ago Both of which we are finding out are apparently insufficient to mitigate this. SoftTalker 10 hours ago "the bug sits in code every Linux server runs when it accepts an IPv4 TCP connection, before any application sees the connection."Is iptables considered an "application" here? I.e. can this bug be triggered before iptables drops the packet? vbezhenar 4 hours ago Put OpenBSD in front to protect that little scared penguin. grey-area 15 hours ago Hoping fix will be out soon so we don’t have to.
stefangordon 14 hours ago Both of which we are finding out are apparently insufficient to mitigate this.
SoftTalker 10 hours ago "the bug sits in code every Linux server runs when it accepts an IPv4 TCP connection, before any application sees the connection."Is iptables considered an "application" here? I.e. can this bug be triggered before iptables drops the packet? vbezhenar 4 hours ago Put OpenBSD in front to protect that little scared penguin.
Both of which we are finding out are apparently insufficient to mitigate this.
"the bug sits in code every Linux server runs when it accepts an IPv4 TCP connection, before any application sees the connection."
Is iptables considered an "application" here? I.e. can this bug be triggered before iptables drops the packet?
Put OpenBSD in front to protect that little scared penguin.
Hoping fix will be out soon so we don’t have to.