This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[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 ]
Nigel Titley
nigel at titley.com
Wed Nov 9 10:38:37 CET 2011
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
- 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 ]