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]/
[db-wg] The New "organisation object" Proposal
- Previous message (by thread): [db-wg] The New "organisation object" Proposal
- Next message (by thread): [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ulrich Kiermayr
ulrich.kiermayr at univie.ac.at
Thu Sep 4 09:22:56 CEST 2003
Hi, One thing (too early to think about all at once) > If we agree on this more generic solution, we could extend this behavior > to other Objects that can be referenced as well. > e.g. for mntner: itself. this would be a way tho prevent anyone from > putting my mntner ont oan object. (This would solve the issue discussed > in the context of the IRT Object - where the mntner of the object should > be a proof of authenticity as well) This idea is good by means of consistency, BUT it would be weaker than the auth: in the IRT, because there are only PGP keys allowed, whereas in a mntner anything is possible. lG uk -- Ulrich Kiermayr Zentraler Informatikdienst der Universitaet Wien Network/Security Universitaetsstrasse 7, 1010 Wien, Austria eMail: ulrich.kiermayr at univie.ac.at Tel: (+43 1) 4277 / 14104 Fax: (+43 1) 4277 / 9140
- Previous message (by thread): [db-wg] The New "organisation object" Proposal
- Next message (by thread): [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]