Re: "changed" field should be deleted

> > I agree that this needs attention.
> > The whole changed: functionality should be reviewed.
> > 
> > I agree that a short term measure could be to suppress changed
> > information unless explicitly requested. This would also allow
> > us to check the whois query logs for those requesting it ...;-).
> > Does anyone know if this would break any knows scripts or uses
> > of the database?
> > 
> > Daniel
> 
> 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.

Then the whole db software could be modified in such a way that
it reponses just a fake line (changed: you-are@localhost 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.

> And if you make the changed: line availables optionally then those
> who want to use addresses will quickly figure out how to get them.

This is true. But if someone knows that the "changed" field is missing
he knows too what is it for. The newbies who write these harrasing
mails know nothing about RIPE database so they won't miss this info.
They will happy without it too. ;-)

This is like medicines. Its are hazardous in hand of a child
so we must keep the drugs locked away. However adults can open
the locker in the bathroom easy if the need some pills.

Regards

Gabor