"changed" field should be deleted
- Previous message (by thread): "changed" field should be deleted
- Next message (by thread): "changed" field should be deleted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael van Elst
mlelstv at xlink.net
Fri Jun 5 17:10:55 CEST 1998
Hello, On Fri, Jun 05, 1998 at 04:58:53PM +0200, kissg at sztaki.hu wrote: > > Hiding the changed: lines definitely breaks every system that keeps > > _copies_ of the entries because it is impossible to update entries > > from these copies without trashing the existing entries. > > I guess the most of these uneducated users use the www interface of the > RIPE-DB and not a client program. > So in the first step it should be filtered out "changed" fields on > the web. This probably doesn't effect the system you wrote about. Agreed. But IMHO there is hardly a problem from people manually looking for these addresses and scripts probably aren't written by 'uneducated users' nor would they get the information from the WWW interface. > Then the whole db software could be modified in such a way that > it reponses just a fake line (changed: you-are at not.interested.in-it 990101) > unless the query contains a "-C almost_secret_password_here" option. > The so called "password" might be retrieved by e-mail > from the RIPE NCC. This would obviously help the registries but other users of the RIPE-DB might be left out by this solution. Greetings, -- i.A. Michael van Elst / phone: +49 721 6635 330 Xlink - Network Information Centre \/ fax: +49 721 6635 349 Vincenz-Priessnitz-Str. 3 /\ link http://nic.xlink.net/ D-76131 Karlsruhe, Germany /_______ email: hostmaster at xlink.net [ Xlink Internet Consulting GmbH, Sitz Koeln ] [ Amtsgericht Koeln HRB 3526, Geschaeftsfuehrer: Michael Rotert ]
- Previous message (by thread): "changed" field should be deleted
- Next message (by thread): "changed" field should be deleted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]