[db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
- Previous message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
- Next message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
virtu virtualabs
virtualabs at gmail.com
Wed Nov 9 10:55:22 CET 2011
So it is up to the community to move from MD5 authentication to stronger authentication methods ? No preventive steps would be taken to avoid MD5 hashes disclosure on the RIPE website ? On Wed, Nov 9, 2011 at 10:38 AM, Nigel Titley <nigel at titley.com> wrote: > On Tue, 2011-11-08 at 15:01 +0100, virtu virtualabs wrote: > > That would mean RIPE NCC did not do anything while people has been > > aware of this fact since 2 years ? > > This problem is well known, both by the RIPE DB working group (which is > what makes the policy, not the RIPE NCC) and also the RIPE NCC itself. > It's been discussed for many years (not just 2) and the use of better > authentication methods has been recommended (and have also been > available for many years). > > However, the community seems to wish to continue to use plain text > passwords in emails, together with MD5 hashing. > > Nigel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20111109/72c6731f/attachment.html>
- Previous message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
- Next message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]