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] action item AP-42.3 - problems of multiple hashed passwords
- Previous message (by thread): [db-wg] [local-ir at ripe.net]Webcast RIPE 45 Announcement
- Next message (by thread): [db-wg] Problems with route object update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Larry J. Blunk
ljb at merit.edu
Wed May 14 11:53:40 CEST 2003
This is an update on AP-42.3 regarding identifying users of multiple hashed passwords (CRYPT-PW or MD5-CRYPT) in a mntner. Merit has implemented an option in it's web-based update form to include an "id" in the comment field of an "auth:" attribute. Additionally, the date and time of creation of the hashed password is included (should one want to keep track of the age of a particular password). Below is an example -- auth: CRYPT-PW Fa1QDrka0aOOM #Id:billg Created:20030514 09:42:45(UTC) As a further note, we have implemented (but not deployed) support for hashed password hiding. When this is deployed, the hash value of a CRYPT-PW will be replaced with the string "HIDDENCRYPTPW" when a mntner object is queried or mirrored. I'm not sure how much of this is of interest to the RIPE community (particularly with the PKI support on the horizon), but I thought I would throw it out for consideration. Regards, Larry Blunk Merit Network
- Previous message (by thread): [db-wg] [local-ir at ripe.net]Webcast RIPE 45 Announcement
- Next message (by thread): [db-wg] Problems with route object update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]