[db-wg] MD5 Hashes in the RIPE Database

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.

Regards,

Denis Walker
Business Analyst
RIPE NCC Database Group

$whois -B DEV-ROOT-MNT

% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf [Open URL]

% Information related to 'DEV-ROOT-MNT'

mntner: DEV-ROOT-MNT
descr: Mntner for DEV-DBM-MNT
admin-c: AA1-DEV
tech-c: AA2-DEV
upd-to: bitbucket at ripe.net
mnt-nfy: bitbucket at ripe.net
auth: MD5-PW # Filtered
auth: PGPKEY-1290F9D2
notify: bitbucket at ripe.net
mnt-by: DEV-ROOT-MNT
referral-by: DEV-ROOT-MNT
remarks: This is an automatically created object.
changed: bitbucket at ripe.net 20051031
source: DEV # Filtered

role: DEV ROLE
nic-hdl: AA2-DEV
address: Somewhere in nowhere
phone: +12 34 567 8900
fax-no: +12 34 567 8900
e-mail: bitbucket at ripe.net
abuse-mailbox: bitbucket at ripe.net
admin-c: AA1-DEV
tech-c: AA2-DEV
mnt-by: DEV-ROOT-MNT
remarks: This is an automatically created object.
changed: bitbucket at ripe.net 20051031
source: DEV

person: Test Person
mnt-by: DEV-ROOT-MNT
address: Somewhere in nowhere
phone: +12 34 5678900
fax-no: +12 34 5678900
e-mail: bitbucket at ripe.net
nic-hdl: AA1-DEV
remarks: This is an automatically created object.
changed: bitbucket at ripe.net 20051031
source: DEV

% This query was served by the RIPE Database Query Service version
1.9-SNAPSHOT (UNDEFINED)