bugtraq - Re: MD5 To Be Considered Harmful Someday

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <41B7699A.5070507@doxpara.com>
Date: Wed, 08 Dec 2004 12:52:42 -0800
From: Dan Kaminsky <dan@...para.com>
To: Paul Wouters <paul@...net.nl>
Cc: Gandalf The White <gandalf@...ital.net>, davids@...master.com,
	BugTraq <bugtraq@...urityfocus.com>
Subject: Re: MD5 To Be Considered Harmful Someday


Paul Wouters wrote:

> On Tue, 7 Dec 2004, Gandalf The White wrote:
>
>> What I am worried about is the integrity of MD5 hashed passwords.  This
>
>
>> It does not matter that I don't know the correct password, I have a 
>> password
>> that collides into the correct hash.  I can log into the system with my
>> generated password.
>
>
> Can't we just truncate the password to 8 characters like in the old days
> before doing the MD5 hash? It will greatly reduce the chance of a 
> collision.
> In fact, I am not even sure my systems don't do this already.
>
Actually, this greatly increases the chance of a collision.  123456789 
will collide with 123456780.

It is unlikely we'll find any ASCII readable payload that collide 
through Wang's search technique.

--Dan