News for hackers. Stuff that matters.
Re:GDB 8.1 Released by rom1v on Wednesday January 31, 2018 @11:54AM (#16275267)
Cool, but why are the release checksums in MD5?
Re:GDB 8.1 Released by dmm on Wednesday January 31, 2018 @12:28PM (#16275543)
MD5 is fine for verifying a download is not corrupted, so that's probably the intended use.
Re:GDB 8.1 Released by lucb1e on Wednesday January 31, 2018 @12:30PM (#16275564)
For that purpose, TCP already includes a CRC32. I'd say cryptographic hashes are generally meant for more than corrupted downloads.
Re:GDB 8.1 Released by tonyg on Wednesday January 31, 2018 @04:59PM (#16277929)
TCP's checksum isn't even as good as CRC32. It's just a one's-complement sum of the packet and a few header words.

From this [0] helpful StackOverflow post:

> If you need to transfer data and you want to be sure the data didn't get corrupted, the TCP checksum alone is certainly not enough for this task. I would even dare to say that a CRC checksum is not enough for this task, since a CRC32 may not detect an error where more than 32 bits in a row are affected (these errors can "cancel out" each other). The minimum checksum you'd need for ensuring flawless data transfer is the MD5 value of the data.

[0] https://stackoverflow.com/questions/3830206/can-a-tcp-checks...

Re:GDB 8.1 Released by alanfranzoni on Wednesday January 31, 2018 @12:32PM (#16275601)
Which is not that hard to fool on large files with multiple, sistemic errors.
Re:GDB 8.1 Released by harikb on Wednesday January 31, 2018 @01:22PM (#16276112)
File checksums are typically used when the checksum is still on the master site but the file could be in untrusted mirrors. TCP level stuff is useless in those scenarios.
Re:GDB 8.1 Released by guipsp on Wednesday January 31, 2018 @02:01PM (#16276496)
So is md5
Re:GDB 8.1 Released by rwmj on Wednesday January 31, 2018 @03:22PM (#16277196)
I have a machine which randomly zeroes blocks of 32 bytes in HTTP downloads [thought to be a cache-related fault] and TCP doesn't catch this.
Re:GDB 8.1 Released by bjoli on Wednesday January 31, 2018 @12:17PM (#16275461)
I don't know, but they also have gpg .sig-files in the download folder.
Re:GDB 8.1 Released by Boxxed on Wednesday January 31, 2018 @02:21PM (#16276695)
Ah yes, the standard nitpicky dismissive HN comment makes its appearance.
Re:GDB 8.1 Released by qubex on Wednesday January 31, 2018 @03:16PM (#16277137)
I’m quite amazed we’ve made it to 33 comments without somebody complaining it the project hasn’t been retooled with Rust/Clojure/Node.js yet.
Re:GDB 8.1 Released by Maken on Thursday February 01, 2018 @12:28PM (#16283733)
There is no point on reimplementing GDB yet, you need first a legacy debugger with proper Rust support until the new one can debug itself.
Re:GDB 8.1 Released by Rexxar on Wednesday January 31, 2018 @09:12PM (#16279243)
I see just a question, nothing "nitpicky dismissive" ? Has the comment been edited into a more neutral tone ?
Re:GDB 8.1 Released by rom1v on Wednesday January 31, 2018 @03:22PM (#16277198)
Fair enough.

I had nothing interesting to say about the new GDB release, but the checksum used surprised me. Hence the question.