[HN Gopher] A new kind of MD5 collision
       ___________________________________________________________________
        
       A new kind of MD5 collision
        
       Author : weinzierl
       Score  : 40 points
       Date   : 2024-03-19 22:07 UTC (53 minutes ago)
        
 (HTM) web link (twitter.com)
 (TXT) w3m dump (twitter.com)
        
       | unilynx wrote:
       | Impressive. Can't have enough nails in the MD5 coffin I guess.
       | 
       | Just had to verify it myself                 echo -n TEXTCOLLBYfG
       | iJUETHQ4hAcKSMd5zYpgqf1YRDhkmxHkhPWptrkoyz28wnI9V0aHeAuaKnak |
       | md5       faad49866e9498fc1719f5289e7a0269            echo -n TEX
       | TCOLLBYfGiJUETHQ4hEcKSMd5zYpgqf1YRDhkmxHkhPWptrkoyz28wnI9V0aHeAua
       | Knak | md5       faad49866e9498fc1719f5289e7a0269
        
       | cosmotic wrote:
       | > 1-byte difference
       | 
       | It's actually just 1 _bit_
        
         | ekzy wrote:
         | True, 01000101 vs 01000001
        
       | TillE wrote:
       | I don't think the title is correct, this isn't "a new kind" of
       | anything. This is the usual well-known attack on MD5 where you
       | can create a pair of inputs with the same hash.
        
       ___________________________________________________________________
       (page generated 2024-03-19 23:00 UTC)