MD5-PW auth scheme is available in the RIPE Database
Dear Colleagues, [apologies for duplicate messages] Following the request from the RIPE Community a new auth scheme based on MD5-crypt algorithm was implemented and put into production today, 16 May 2002. Implementation details can be found in the proposal circulated in the db-wg mailing list http://www.ripe.net/ripe/mail-archives/db-wg/20020401-20020701/msg00011.html. We also created another FAQ entry "How to use MD5-PW auth scheme in my mntner?" (http://www.ripe.net/ripencc/faq/database/qa5.html#13). The RIPE Database Reference Manual will be updated soon. You may use Crypt CGI interface (http://www.ripe.net/cgi-bin/cgicrypt.pl.cgi) to convert your passphrase to MD5-PW string. Regards, Andrei Robachevsky DB Group RIPE NCC
Dear Colleagues, [apologies for duplicate messages] Following the request from the RIPE Community a new auth scheme based on MD5-crypt algorithm was implemented and put into production today, 16 May 2002. Implementation details can be found in the proposal circulated in the db-wg mailing list http://www.ripe.net/ripe/mail-archives/db-wg/20020401-20020701/msg00011.html. We also created another FAQ entry "How to use MD5-PW auth scheme in my mntner?" (http://www.ripe.net/ripencc/faq/database/qa5.html#13). The RIPE Database Reference Manual will be updated soon. You may use Crypt CGI interface (http://www.ripe.net/cgi-bin/cgicrypt.pl.cgi) to convert your passphrase to MD5-PW string. Regards, Andrei Robachevsky DB Group RIPE NCC
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? -- Met vriendelijke groet, __________________ Sabri Berisha /\ ___/ SAB666-RIPE /- \ _/ Business Internet Trends BV http://noc.bit.nl/ /--- \/ __________________
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@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?
participants (3)
-
Andrei Robachevsky -
andrei＠ripe.net
-
Sabri Berisha