Re:Linux kernel bug delivers corrupt TCP/IP data
by vijayp on Friday February 12, 2016 @10:28AM
(#11087818)
Yeah, TCP's checksum is indeed weak and TLS is indeed a good answer.
However, I think delusional is a bit of a strong word to use here. "Performance of Checksums and CRCs over Real Data" has a bunch of interesting data about the number oand types of common errors detected by simple checkums and CRC: http://ccr.sigcomm.org/archive/1995/conf/partridge.pdf
Re:Linux kernel bug delivers corrupt TCP/IP data
by russdill on Friday February 12, 2016 @07:34PM
(#11091740)
You misunderstand the purpose of checksums. Checksums and error correcting codes do no eliminate errors, they reduce the frequency of undetected errors by a known factor.
If a system was designed with the usage of TCP checksums in mind, then removing TCP checksums will create a system with an error rate 4 orders of magnitude higher than before.
Re:Linux kernel bug delivers corrupt TCP/IP data
by wyldfire on Friday February 12, 2016 @11:50AM
(#11088523)
Does SCTP have a better CRC/checksum than TCP?
EDIT: yes, it does. As of RFC 3309, it uses CRC32c (the one which has an instruction in SSE).
Re:Linux kernel bug delivers corrupt TCP/IP data
by felixge on Friday February 12, 2016 @11:39AM
(#11088431)
Does TLS support transparent retransmits of corrupted packets?
Re:Linux kernel bug delivers corrupt TCP/IP data
by vijayp on Friday February 12, 2016 @12:13PM
(#11088685)
http://blog.cryptographyengineering.com/2012/01/attack-of-we...
This article talks about tls and corruption, including dtls. I found it educational!
Re:Linux kernel bug delivers corrupt TCP/IP data
by vbezhenar on Friday February 12, 2016 @11:42AM
(#11088452)
I don't think so. Probably it'll just reset connection.
Re:Linux kernel bug delivers corrupt TCP/IP data
by felixge on Friday February 12, 2016 @11:47AM
(#11088500)
I guess that's arguably better than accepting corrupted data, but still a step backwards from the abstraction TCP is intended to provide in regards to checksums ...
Re:Linux kernel bug delivers corrupt TCP/IP data
by yeukhon on Friday February 12, 2016 @01:01PM
(#11089049)
TCP checksum and TLS checksum/macing both have use case. Not every protocol built on TCP supports TLS. If TCP checksum is broken, we have to fix it. So I agree with below delusional is too strong. If a simple checksum is buggy, how can I trust anything about said TCP protocol implementation? How can you reassure other data integrity implementation isn't buggy? This bug isn't really about whether TCP checksum is weak or not, rather, just a bug which I suppose most people ignore.
Re:Linux kernel bug delivers corrupt TCP/IP data
by SFjulie1 on Friday February 12, 2016 @11:34AM
(#11088388)
checksums are cost efficient for detecting statistically HW errors.
It is just no modern engineers seems to care to check the checksums.
Re:Linux kernel bug delivers corrupt TCP/IP data
by arca_vorago on Friday February 12, 2016 @11:10AM
(#11088204)
Which only makes me more curious about piping things over udp, tcp included.
That is why link layers always have other stronger CRCs too.
This is actually one of the better reasons to always use TLS. Yhe MAC authentication it uses is much stronger.