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/
MD5-PW auth scheme is available in the RIPE Database
- Previous message (by thread): MD5-PW auth scheme is available in the RIPE Database
- Next message (by thread): Phasing out MAIL-FROM auth scheme
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrei Robachevsky
andrei at ripe.net
Fri May 17 10:06:06 CEST 2002
Dear Sabri Berisha, This happened because your client only yesterday made about 15000 queries for various IP numbers collecting contact information. This resulted in automatic blocking of that client. Please contact the Database Administration ripe-dbm at ripe.net to discuss your application. Regards, Andrei Robachevsky DB Group Manager RIPE NCC Sabri Berisha wrote: > On Thu, 16 May 2002, Andrei Robachevsky wrote: > > 8< md5 stuff > > It seems that this is not the only change in the database. Doing a whois > on 193.109.122.2 gives: > > (inetnum) > (route) > > %ERROR:202: access control limit reached > % > % You have reached the limit of returned contact information objects. > % This connection will be terminated now. > % Continued attempts to return excessive amounts of contact > % information will result in permanent denial of service. > % Please do not try to use CONTACT information in > % the RIPE database for non-operational purposes. > % Refer to http://www.ripe.net/ripencc/pub-services/db/copyright.html > % for more information. > > instead of the person/role objects. > > Why is this? > >
- Previous message (by thread): MD5-PW auth scheme is available in the RIPE Database
- Next message (by thread): Phasing out MAIL-FROM auth scheme
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]