[db-wg] MD5 Hashes in the RIPE Database
- Previous message (by thread): [db-wg] MD5 Hashes in the RIPE Database
- Next message (by thread): [db-wg] rpsltool & odd prefixes in the RIPE db
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Denis Walker
denis at ripe.net
Wed May 23 14:31:13 CEST 2012
Dear Colleagues, This revised implementation has now been deployed. If you have any specific issues with it, please contact our Customer Services with details on <ripe-dbm at ripe.net>, or for more general comments you can reply back to this mailing list. Regards, Denis Walker Business Analyst RIPE NCC Database Group On 16/05/12:21 12:35 PM, Nigel Titley wrote: > On 26/04/2012 10:25, Denis Walker wrote: >> Dear colleagues, >> >> It was clear from the discussions at RIPE 64 that we need to change the >> initial implementation of hiding the hashes for MD5 passwords in MNTNER >> objects. A suggestion was made to keep the "auth:" attributes in place. >> If the authentication token is an MD5 password we will remove the hash >> value. All PGP and X.509 values will remain unchanged. >> >> We have already worked on this and a sample MNTNER object would look >> like the object below. We can deploy this change within the next two >> weeks. >> > I've noted 6 replies in favour of this and none against and so I'd ask > the DB team to roll this change out as soon as conveniently possible. > > Nigel > > >
- Previous message (by thread): [db-wg] MD5 Hashes in the RIPE Database
- Next message (by thread): [db-wg] rpsltool & odd prefixes in the RIPE db
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]