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] Suggestion for a way to retrieve filtered objects
- Previous message (by thread): [db-wg] Suggestion for a way to retrieve filtered objects
- Next message (by thread): [db-wg] Plain text passwords in email updates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hank Nussbacher
hank at efes.iucc.ac.il
Thu Feb 16 06:35:17 CET 2012
> > Do you need to specify any special options to whois to get the auth: > > lines from the maintainer object? We have a maintainer object where > > I'm pretty sure that all the auth: lines are of PGP- style, but whois > > is still not displaying those lines. Trying to use > > > > https://apps.db.ripe.net/webupdates/search.html > > > > it asks me for "password". What password?!? No, I have not used > > webupdates before, and have no particular desire to start using it > > now. Is there no way around this? > > > > I really, Really, dislike this change in behaviour, since we are now > > effectively cut off from updating our maintainer object -- we keep no > > local copy of the object, and want to use the one stored in the RIPE > > database as the authoritative data source. Now we can't do that. > > Argh! Ditto. The one time I tried to use webupdates (3 days ago), I hit a bug. See the comments at the end: https://labs.ripe.net/Members/denis/securing-md5-hashes-in-the-ripe-database -Hank
- Previous message (by thread): [db-wg] Suggestion for a way to retrieve filtered objects
- Next message (by thread): [db-wg] Plain text passwords in email updates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]