[db-wg] Deprecation of CRYPT-PW authentication method from the RIPE Database:Start of Phase 2

[Agoston Horvath <]

[Apologies for duplicate mails]

Dear Colleagues,

Phase 2 of the CRYPT-PW deprecation project will start today, Wednesday, 
10 January 2007.

During this period the following will apply:

   * Any modification to a maintainer or IRT object that adds a new 
CRYPT-PW authentication will be rejected
   * Any modification to a maintainer or IRT object that attempts to 
replace a CRYPT-PW with another CRYPT-PW will be rejected
   * Any object creations that include a CRYPT-PW authentication will 
be rejected
   * The RIPE Database will add a warning to the acknowledgement 
message if CRYPT-PW is used during authentication
   * The RIPE Database will add a warning to the acknowledgement 
message if a modified maintainer or IRT object still contains existing 
CRYPT-PW authentication

Notification e-mails will be sent today to over 6300 e-mail addresses, 
concerning a total of 2778 objects with CRYPT-PW authentication only. 
Another 252 objects have other authentication methods in addition to 
CRYPT-PW. 20898 maintainers have no CRYPT-PW password at all.

If you receive a separate notification e-mail you will have to change 
your password authentication method to PGP, X.509 or MD5-PW.

To change your password authentication method from CRYPT-PW to MD5-PW, 
use the CGI at:
https://www.ripe.net/cgi-bin/crypt2md5.cgi

Phase 1 of the project has been successfully completed. One quarter of 
all objects containing CRYPT-PW authentication have been modified. Over 
85% of these changes were made using the crypt2md5.cgi web form.

More information about the project is available at:
http://www.ripe.net/db/support/security/crypt-pw_deprecation/

*Key dates*
Thursday, 30 November 2006: Notification (Phase 1)
Wednesday, 10 January 2007: Reject new CRYPT-PW (Phase 2)
Wednesday, 21 February 2007: Remove CRYPT-PW from RIPE Database (Phase 3)

If you have any questions, contact: ripe-dbm@localhost.

Regards,
Agoston Horvath
Database Group
RIPE NCC