top | item 20208519 (no title) rphlx | 6 years 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. discuss order hn newest jontro|6 years ago They found a bug in FreeBSD too: https://github.com/Netflix/security-bulletins/blob/master/ad... temprature|6 years ago That's in Netflix's custom stack that they contributed to freebsd, and not used by default. loeg|6 years ago FWIW the FreeBSD bug only affects the RACK tcp algorithm, which isn’t the default (I think). load replies (1)
jontro|6 years ago They found a bug in FreeBSD too: https://github.com/Netflix/security-bulletins/blob/master/ad... temprature|6 years ago That's in Netflix's custom stack that they contributed to freebsd, and not used by default. loeg|6 years ago FWIW the FreeBSD bug only affects the RACK tcp algorithm, which isn’t the default (I think). load replies (1)
temprature|6 years ago That's in Netflix's custom stack that they contributed to freebsd, and not used by default.
loeg|6 years ago FWIW the FreeBSD bug only affects the RACK tcp algorithm, which isn’t the default (I think). load replies (1)
jontro|6 years ago
temprature|6 years ago
loeg|6 years ago