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]/

Deprecation of the MAIL-FROM auth scheme

Previous message (by thread): MD5 proposal
Next message (by thread): Deprecation of the MAIL-FROM auth scheme

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

Janos Zsako zsako at banknet.net
Mon Apr 1 00:38:19 CEST 2002

>   From owner-db-wg at ripe.net Mon Mar 25 13:58:43 2002
>   From: Andrei Robachevsky <andrei at ripe.net>

Andrei,

>   In case a mntner contains only one "auth" scheme, which is MAIL-FROM, it
>   will be replaced with a CRYPT-PW scheme with a DES string that cannot be
>   matched.

Why don't you add "CRYPT-PW azsLXaNunJ9Rs", which is the auth of
RIPE-NCC-HM-MNT? This way the hostmaster team could easily update a mntner
object when the "authorized and authenticated" maintainer shows up and asks
you to perform the update ("authorized and authenticated" above
refers to the procedure you have in place for dealing with such cases.)

Best regards,
Janos

PS. Otherwise, I guess you need a special mechanism to update such "orphaned"
maintainers...

Previous message (by thread): MD5 proposal
Next message (by thread): Deprecation of the MAIL-FROM auth scheme

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

[ db-wg Archives ]