Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of h.reindl@thelounge.net
 designates 91.118.73.15 as permitted sender)
Message-ID: <4FE247B0.7030403@thelounge.net>
Date: Wed, 20 Jun 2012 23:59:12 +0200
From: Reindl Harald <h.reindl@thelounge.net>
Organization: the lounge interactive design
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: md5crypt passwords
References: 
 <CAMD-=VJS7f49CoCjMvhz0j8t=uf2xnaaCuxkA36J34brj2OoyQ@mail.gmail.com>
 <4FE23E60.6010701@thelounge.net> <4FE240BE.2090402@thelounge.net>
 <201206202352.23957.sf@sfritsch.de>
In-Reply-To: <201206202352.23957.sf@sfritsch.de>
OpenPGP: id=7F780279;
	url=http://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig71F54CF51EDA16050483AE15"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig71F54CF51EDA16050483AE15
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable


Am 20.06.2012 23:52, schrieb Stefan Fritsch:
>> you do not need the original password!
>> you only need a hash-collision and can leave out
>> special chars completly to find one
>=20
> You need a password that gives the same value after 1000 rounds of=20
> md5(password md5(password md5(password ...))). This is much more=20
> expensive to find with brute force than a password that gives a=20
> collision for a single md5

everybody with crypto knowledge will explain you that you
are totally wrong - i can only try in my words!

in the context of a hash-collision and rainbow-tables
you need any string producing the same hash, no matter
if 1, 10 or 1000 times md5() recursion

there is a reason why even the developer of md5crypt
saw the need for a offical statement that md5crypt
should never again be considered as secure in any case!

-------- Original-Nachricht --------
Betreff: CVE-2012-3287: md5crypt is no longer considered safe
Datum: Fri, 8 Jun 2012 00:04:49 GMT
Von: phk@FreeBSD.org
An: bugtraq@securityfocus.com

The LinkedIn password incompetence has resulted in a number of "just use =
md5crypt and you'll be fine" pieces of
advice on the net.

Since I no longer consider this to be the case, I have issued an official=
 statement, as the author of md5crypt, to
the opposite effect:

http://phk.freebsd.dk/sagas/md5crypt_eol.html

Please find something better now.

Thanks for using my code.

Poul-Henning Kamp


--------------enig71F54CF51EDA16050483AE15
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/iR7EACgkQhmBjz394AnlExQCfZj1IeZrHxLUSXsIImEN/AYMA
72AAmwSgFDEsGbM69M7rkgkwkw/bAvoA
=MJIM
-----END PGP SIGNATURE-----

--------------enig71F54CF51EDA16050483AE15--