News for hackers. Stuff that matters.
Re:DragonFly BSD 5.2 by noselasd on Saturday April 14, 2018 @10:30AM (#16837446)
The issue is that if these files are distributed elsewhere by 3. parties, it is trivial for those 3. parties change and compromise the files, but still make the files produce the same MD5 sum.
Re:DragonFly BSD 5.2 by temprature on Saturday April 14, 2018 @07:24PM (#16840162)
If you think a preimage attack against MD5 is "trivial" you should demonstrate it. People would be very interested in this because no one has managed to do it yet.

Creating two files with the same MD5 is a very different beast from creating a file with the same MD5 as an arbitrary pre-existing file. These third parties would need to have colluded with the DragonFly developers to make what you're proposing possible.

Re:DragonFly BSD 5.2 by hawski on Saturday April 14, 2018 @11:43AM (#16837781)
Wouldn't it be easier for said third parties to just distribute changed checksum?
Re:DragonFly BSD 5.2 by noselasd on Tuesday April 17, 2018 @06:21PM (#16862817)
Then it would also be trivial to discover if you go and look up the sums at the official site.