20 ms·

What does OpenBSD/NetBSD do differently to not be affected by this?

• rphlx 7y ago
  They use a different TCP/IP stack which implemented SACK without introducing this bug. It's a Linux-specific implementation defect, not an intrinsic problem with the TCP SACK wire protocol or spec.
  • jontro 7y ago
    They found a bug in FreeBSD too: https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-001.md#2-cve-2019-11478-sack-slowness-linux--415-or-excess-resource-usage-all-linux-versions https://github.com/Netflix/security-bulletins/blob/master/ad...
    • loeg 7y ago
      FWIW the FreeBSD bug only affects the RACK tcp algorithm, which isn’t the default (I think).
      • bifrost 7y ago
        Correct, its not enabled by default.
    • temprature 7y ago
      That's in Netflix's custom stack that they contributed to freebsd, and not used by default.