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/[email protected]/
FW: FW: [db-wg] Proposal to deprecate CRYPT-PW authorisation in the RIPE Database
- Previous message (by thread): FW: [db-wg] Proposal to deprecate CRYPT-PW authorisation in the RIPE Database
- Next message (by thread): FW: FW: [db-wg] Proposal to deprecate CRYPT-PW authorisation in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Potapov Vladislav
poty at iiat.ru
Thu Oct 5 11:51:35 CEST 2006
Hi, > From: Gert Doering [mailto:gert at space.net] > Changing from CRYPT-PW to MD5-PW doesn't incur any > operational changes, and doesn't require key management and > crypto of any sort, but *will* improve security. No "operational changes"? Let's look at the plan to get an image that it's not so "problemless". I don't speak about RIPE resources which should support this change. About security: there was several opponents of your view already. I'm adding myself to them. > From: Gert Doering [mailto:gert at space.net] > Security issues in the IRR DB impact all of us (like "fake objects, > use that to leverage a routing attack"). Let's not say fairy tales about that. I have asked about REAL LIFE problems with the scheme. Nobody has answered. As for security issues... I think the better way to do this things is to educate people, convince them to have better way of security. Up to now it is only "small group words" and 3500 usages... I'm against the proposal. Vladislav Potapov Ru.iiat
- Previous message (by thread): FW: [db-wg] Proposal to deprecate CRYPT-PW authorisation in the RIPE Database
- Next message (by thread): FW: FW: [db-wg] Proposal to deprecate CRYPT-PW authorisation in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]