Re: Massive changed in the Ripe Database..
Thus wrote Mike Norris (mike.norris@heanet.ie):
well we should collect money for Mr. McBryan to spend him a two-week-last-minute-trip to ... lets say mallorca without internet access, then the community has time to fix all the mistakes he made :-)))
Maybe he's signed up for one of the RIPE Local IR training courses; wouldn't that be a lot better?
shoot him to the moon? :-3 Would suit my feelings better .. anyone can err, but then messing with my repair work by faking our headers is way off bounds. This whole little escapade cost Xlink about 3 man-days work, and we're not finished mopping up yet. kind regards, Petra Zeidler -- [X] Xlink Internet Service GmbH | | i.A. Petra Zeidler, Neukundenanschluss | zeidler@xlink.net | | Vincenz-Prie_nitz-Stra_e 3 [X] D-76131 Karlsruhe | Tel: 0721/9652-220 [X] Fax: 0721/9652-209 | | Geschdftsf|hrer: Michael Rotert. Amtsgericht Karlsruhe HRB 8161. | Auftrdge erledigen wir zu unseren Allgemeinen Geschdftsbedingungen. ---------------------------------------------------------------------[ ]
On Fri, Oct 30, 1998 at 04:54:50PM +0100, Petra Zeidler wrote: : shoot him to the moon? :-3 Would suit my feelings better .. anyone can : err, but then messing with my repair work by faking our headers is way off : bounds. : This whole little escapade cost Xlink about 3 man-days work, and we're not : finished mopping up yet. Well....I think, we must have another database access. My ideas: 1. No Public Access to the Database I think, we have all (and our customers) problems (with email spam, and the normal snail mail spam. Many of the addresses are only in the RIPE DB. 2. Protection of the RIPE DB Objects Well, we can protect the person objects with our mnt objects. if anyone change the local ir, the old local ir can change the mnt entry in the object to the new local ir. 3. special work with person objects the only way to create, modify and delete person objects is the way to create, modify and delete person objects at a regional IR (denic@germany etc.). Non-Members of regional IR can only create, modify and delete person templates @ the local ir, where they register domains, or register ip networks. 4. Special work with RIPE objects in common what about a timestamped list of requests to the RIPE DB ? If anyone wants to delete objects, and do it in an interval of 10 deletions in 5 seconds (or any other interval we can discuss), the deletions are rejected and the person who request the delete is asked: "Why ?" these 4 points are just ideas...dunno if we can deploy it, but I think we can discuss several problems with the RIPE DB, and think about a solution of the problems. My 2Cent :) sh -- Stephan Hermann, techn. Leiter eMail office: sh@nwu.de NWU GmbH, Am Brambusch 1, D-44536 Luenen home : sh@linux.de Sales: Widumer Str. 28, D-44339 Dortmund Tel.: +49-231-9809110 sales-eMail: vertrieb@nwu.de FAX : +49-231-98091120
Hi all,
1. No Public Access to the Database I think, we have all (and our customers) problems (with email spam, and the normal snail mail spam. Many of the addresses are only in the RIPE DB.
I have indeed found my own RIPE entries indexed on WWW search engines, which I find a violation of the copyright. However, one very significant purpose of the RIPE DB (IMHO) is that it is available for trouble-shooting. This makes it necessary to give ISPs/IAPs access to it. In other words, you might as well make it public.
4. Special work with RIPE objects in common what about a timestamped list of requests to the RIPE DB ? If anyone wants to delete objects, and do it in an interval of 10 deletions in 5 seconds (or any other interval=20 we can discuss), the deletions are rejected and the person who request the delete is asked: "Why ?"
Same goes for all types of object, doesn't it ? Yeah, well... I got a message yesterday asking me to stop flooding one one the RIPE robots, just because I sent a batch of perfectly legitimate update requests. I'm afraid that idea doesn't work, either. Bernard
Stephan Hermann wrote:
1. No Public Access to the Database I think, we have all (and our customers) problems (with email spam, and the normal snail mail spam. Many of the addresses are only in the RIPE DB.
The problem here is that RIPE is a very usefull resource for the whole Internet community. Personally I have not had much of a problem with spam sent to email addresses on the database so I do not know how much of a problem this is. -- Leigh
hi, Am/Um 10:23 04.11.98 +0000 Leigh Porter schrieb:
Stephan Hermann wrote:
1. No Public Access to the Database I think, we have all (and our customers) problems (with email spam, and the normal snail mail spam. Many of the addresses are only in the RIPE DB.
The problem here is that RIPE is a very usefull resource for the whole Internet community. Personally I have not had much of a problem with spam sent to email addresses on the database so I do not know how much of a problem this is.
Well, the first task of the RIPE DB is to show the isps who is responsible for domains, ip networks, etc. But, in the time of collecting informations about people (not only netizens),the ripe db is for address collectors the first place in the net. In Germany (I don't know how it is in other countries) you can deny the print or announcement of your postal address in public addressbooks. the ripe db is sometimes like a public addressbook. but the persons can't deny the publication of their addresses if they register a domain or something like that. So, the solution must be to secure the dates in the database. Ok, in the database output you can find the copyright statement...but it's only a statement...and you can say if you have the address out of the db: "I found this address on the persons webpage, or in one usenet article" who can determine if this statement is right or wrong ? imho we (ripe/ncc, local/regional ir etc.) must enforce the copyright...if we can't do it with rules, then we must protect the database with technical solutions against the abuse. anyone who wants informations about a specific topic (here: persons, administrating contacts etc.) can ask the local/regional ir, the ripe/ncc. kind regards, sh -- Stephan Hermann eMail: sh@nwu.de priv: sh@linux.de Tel: 0231/9809-1113 techn. Leiter http://www.nwu.de/ Fax: 0231/9809-1120 Hauptsitz : NWU GmbH, Am Brambusch 1, D-44536 Luenen Vertriebsbuero: NWU GmbH, Widumer Str. 28, D-44339 Dortmund
In message <36402B0F.F64BD43C@wisper.net>, Leigh Porter writes:
Stephan Hermann wrote:
1. No Public Access to the Database I think, we have all (and our customers) problems (with email spam, and the normal snail mail spam. Many of the addresses are only in the RIPE DB.
The problem here is that RIPE is a very usefull resource for the whole Internet
community. Personally I have not had much of a problem with spam sent to email addresses on the database so I do not know how much of a problem this is.
I think a far better long term strategy would be to sue the pants of people who trespass on the database... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
participants (6)
-
Bernard Steiner -
Leigh Porter -
Petra Zeidler -
Poul-Henning Kamp -
sh＠nwu.de -
Stephan Hermann