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/[email protected]/
[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] MD5 Hashes in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Freedman
david.freedman at uk.clara.net
Fri Apr 27 19:51:43 CEST 2012
+1 Dave On 27 Apr 2012, at 15:47, "Sascha Lenz" <slz at baycix.de> wrote: > Hi, > >> 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 would very much like to see this implemented :-) > > Although i made myself comfortable with the current "new" way of doing updates > by mail, it's annoying and certainly safes time to be able to do that again > in one step like we used to. > > Thanks for this! > > -- > Mit freundlichen Grüßen / Kind Regards > > Sascha Lenz [SLZ-RIPE] > Senior System- & Network Architect > > > > >
- Previous message (by thread): [db-wg] MD5 Hashes in the RIPE Database
- Next message (by thread): [db-wg] MD5 Hashes in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]