[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 ]
David Freedman
david.freedman at uk.clara.net
Wed Nov 9 15:38:41 CET 2011
I have already submitted a pair of policy proposals to the db-wg chairs, am awaiting their response. Dave. On 09/11/2011 14:35, "Nigel Titley" <nigel at titley.com> wrote: >On Wed, 2011-11-09 at 10:55 +0100, virtu virtualabs wrote: >> 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 ? > >The community has so far decided that it is quite happy with the MD5 >disclosure on the web site. If you want to create a policy proposal to >change this then please go ahead. I suggest you raise it on this list >first of all, then if you see a degree of support enlist the help of the >RIPE NCC in creating the proposal (Emilio is the policy officer and will >be delighted to help). > >All the best > >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 ]