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] Updating maintainer objects with filtered auth lines
- Previous message (by thread): [db-wg] Updating maintainer objects with filtered auth lines
- Next message (by thread): [db-wg] Updating maintainer objects with filtered auth lines
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco d'Itri
md at Linux.IT
Fri Aug 21 18:10:13 CEST 2015
On Aug 21, denis <ripedenis at yahoo.co.uk> wrote: > Maybe I can bounce this back at you in the form of another question...who > does this password belong to that you don't want to disturb? It sounds like > you don't know who has access to this data. Shared mntner objects: we had the same issue (and no good solution) with the ones used to protect the 6to4 and Teredo objects. But I recently experienced this also with a company mntner: I do not know and I am not supposed to know the password used by my colleagues, but I also did not have around a local copy of the object (which looks like a bad idea to me, since it could easily get out of sync with the one in the database). A simple (at least for the end users...) solution would be to allow retrieving the unfiltered objects with a PGP-authenticated emails. -- ciao, Marco -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 648 bytes Desc: not available URL: </ripe/mail/archives/db-wg/attachments/20150821/4a320f0a/attachment.sig>
- Previous message (by thread): [db-wg] Updating maintainer objects with filtered auth lines
- Next message (by thread): [db-wg] Updating maintainer objects with filtered auth lines
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]