[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] call for application authorisation ideas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Stolpe
stolpe at resilans.se
Mon Aug 24 13:44:46 CEST 2015
On Fri, 21 Aug 2015, Marco d'Itri wrote: > 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. I totally agree. Cheers, Daniel _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe at resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 45 094 556741-1193 104 30 Stockholm
- Previous message (by thread): [db-wg] Updating maintainer objects with filtered auth lines
- Next message (by thread): [db-wg] call for application authorisation ideas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]