News for hackers. Stuff that matters.
Re:RFC 6920: Naming Things with Hashes by dchest on Sunday February 21, 2016 @04:55AM (#11143948)
Which basically means that it guarantees the integrity of message, where "guarantee" is defined as computational infeasibility to produce different messages with the same hash value. You know this stuff, why are you arguing semantics?
Re:RFC 6920: Naming Things with Hashes by jjtheblunt on Sunday February 21, 2016 @12:19PM (#11145362)
I hear you regarding infeasibility, though right now there's another article about content hash collisions being used to distribute a tampered-with Mint Linux image (MD5 collisions).

It's "easier" to get the computational resources to fabricate a collision there, of course, but who is to say how much compute power state level adversaries bring to bear?

Re:RFC 6920: Naming Things with Hashes by dchest on Sunday February 21, 2016 @04:03PM (#11146512)
To be fair, MD5 was broken in 1996. If your content addressable system uses crypto broken 10 years ago, of course, you can't guarantee integrity :-)

who is to say how much compute power state level adversaries bring to bear

Not enough to break modern hash functions.