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] MD5s of the RIPE database, Deprecation of MD5 and safe authentication methods

• Previous message (by thread): [db-wg] MD5s of the RIPE database, Deprecation of MD5 and safe authentication methods
• Next message (by thread): [db-wg] MD5s of the RIPE database, Deprecation of MD5 and safe authentication methods

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Martin Gollowitzer mg at kapper.net
Tue Jul 14 11:35:31 CEST 2015

Hi,

> Poor implementation of a good idea.

I beg to differ.

> Now expects a wave of applications for the restoration of access to mnt- objects.

Well, the process is not too complicated.

> E-mail newsletter for these maintainer you tried to do?

The affected maintainers were contacted beforehand. We had one customer who contacted us about it. They didn't even know their password anymore, so the restoration process had to be done anyway.

> Where instructions to restore access?

See the database FAQ.
 
All the best,
Martin

• Previous message (by thread): [db-wg] MD5s of the RIPE database, Deprecation of MD5 and safe authentication methods
• Next message (by thread): [db-wg] MD5s of the RIPE database, Deprecation of MD5 and safe authentication methods

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]