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] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database

Previous message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
Next message (by thread): [db-wg] Displaying RegID for all resources

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

Alexander Zubkov green at msu.ru
Tue Nov 15 10:31:21 CET 2011

 > There is always starttls - which RIPE already supports.  But you 
cannot be
 > guaranteed that it is turned on at the client site, or that both sides
 > actually perform validation of each others' certs.  Any sensible mail 
admin
 > will enable it.

Problem with sending mail securely to RIPE DB's server can be solved 
with encrypted e-mail. But as I know, there is no this possibility yet.
I think this is more reliable way, then making sure mail will go in SSL 
channels all way long.
In addition, crypted mail and TLS connections are not preventing each 
other. And can be used together. :)

Previous message (by thread): [db-wg] Disallowing MD5 passwords in e-mail updates, was MD5 Hashes in the database
Next message (by thread): [db-wg] Displaying RegID for all resources

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

[ db-wg Archives ]