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] crypted password

Previous message (by thread): [db-wg] crypted password
Next message (by thread): [db-wg] crypted password

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

Wilfried Woeber, UniVie/ACOnet Woeber at CC.UniVie.ac.at
Tue Jul 25 12:33:48 CEST 2006

Max et.al.

before digging deeper and commenting on more general aspects,
do I understand it correctly that ...

Max Tulyev wrote:
[...]
> My view:
> 
> - Implement md5-pw object in database
> - Autocreate md5-pw objects for all existing md5 passwords
> - Autochange hashed passwords with md5-pw objects
> - Include "remark: see http://... for what's happened" in chaned objects
> 
> Like it was in person/org objects when russian area phone codes was
> changed.

... you basically propose to align _all_ authentication mechanisms in the sense
that the necessary information to check credentials is stored in a _separate_,
dedicated object, like it is done already for PGP and X509?

Wilfried.

Previous message (by thread): [db-wg] crypted password
Next message (by thread): [db-wg] crypted password

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

[ db-wg Archives ]