From roger.kristiansen at redpill-linpro.com Fri Sep 16 15:16:51 2011 From: roger.kristiansen at redpill-linpro.com (Roger Kristiansen) Date: Fri, 16 Sep 2011 15:16:51 +0200 Subject: REST API woes Message-ID: <4E734C43.8030309@redpill-linpro.com> Hi, First of all: I'm not sure if this is the correct mailing list for questions regarding the Database REST API. If it isn't then I'm sorry, and I hope you might point me in the right direction. I am in need of API access to the RIPE database, both for querying and updating. I have been looking at the REST API documented at http://labs.ripe.net/ripe-database/database-api/api-documentation. I can connect, but I am unable to get a response from the lab.db.ripe.net server. No error or anything else. I'm accessing the server from the address 193.69.55.146. Here's one example, using curl on one of your example URLs: $ curl -v http://lab.db.ripe.net/whois/lookup/ripe/mntner/RIPE-DBM-MNT * About to connect() to lab.db.ripe.net port 80 (#0) * Trying 193.0.19.31... connected * Connected to lab.db.ripe.net (193.0.19.31) port 80 (#0) > GET /whois/lookup/ripe/mntner/RIPE-DBM-MNT HTTP/1.1 > User-Agent: curl/7.21.3 (i686-pc-linux-gnu) libcurl/7.21.3 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 > Host: lab.db.ripe.net > Accept: */* > .. then nothing. Anyone know what might be wrong here? Also I'm not quite sure where or how to get the required password to perform updates. Any pointers? Would be much appreciated. :-) Regards, Roger Kind Kristiansen From roger.kristiansen at redpill-linpro.com Fri Sep 16 15:58:33 2011 From: roger.kristiansen at redpill-linpro.com (Roger Kristiansen) Date: Fri, 16 Sep 2011 15:58:33 +0200 Subject: REST API woes In-Reply-To: <4E734C43.8030309@redpill-linpro.com> References: <4E734C43.8030309@redpill-linpro.com> Message-ID: <4E735609.2020209@redpill-linpro.com> The first part of this question can be disregarded, as I got confirmation that the server is indeed down ATM. Still wondering about the password, though, so.. anyone? :-) Regards, Roger Kind Kristiansen On 09/16/2011 03:16 PM, Roger Kristiansen wrote: > Hi, > > First of all: I'm not sure if this is the correct mailing list for > questions regarding the Database REST API. If it isn't then I'm sorry, > and I hope you might point me in the right direction. > > I am in need of API access to the RIPE database, both for querying and > updating. I have been looking at the REST API documented at > http://labs.ripe.net/ripe-database/database-api/api-documentation. > > I can connect, but I am unable to get a response from the > lab.db.ripe.net server. No error or anything else. I'm accessing the > server from the address 193.69.55.146. > > Here's one example, using curl on one of your example URLs: > > $ curl -v http://lab.db.ripe.net/whois/lookup/ripe/mntner/RIPE-DBM-MNT > * About to connect() to lab.db.ripe.net port 80 (#0) > * Trying 193.0.19.31... connected > * Connected to lab.db.ripe.net (193.0.19.31) port 80 (#0) >> GET /whois/lookup/ripe/mntner/RIPE-DBM-MNT HTTP/1.1 >> User-Agent: curl/7.21.3 (i686-pc-linux-gnu) libcurl/7.21.3 > OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 >> Host: lab.db.ripe.net >> Accept: */* >> > > .. then nothing. Anyone know what might be wrong here? > > Also I'm not quite sure where or how to get the required password to > perform updates. Any pointers? Would be much appreciated. :-) > > > Regards, > Roger Kind Kristiansen > -- Roger Kristiansen Redpill Linpro AS - Changing the game Mobil: +47 917 88 471 From denis at ripe.net Fri Sep 16 16:56:02 2011 From: denis at ripe.net (Denis Walker) Date: Fri, 16 Sep 2011 16:56:02 +0200 Subject: REST API woes In-Reply-To: <4E735609.2020209@redpill-linpro.com> References: <4E734C43.8030309@redpill-linpro.com> <4E735609.2020209@redpill-linpro.com> Message-ID: <4E736382.20602@ripe.net> Dear Roger Kind Kristiansen, I am assuming your question is "how to get the required password 'into the update engine' to perform updates?" Passwords are sent as HTTP parameters, for example https://lab.db.ripe.net/whois/modify///?password=... regards Denis Walker Business Analyst RIPE NCC Database Group On 16/09/11:38 3:58 PM, Roger Kristiansen wrote: > The first part of this question can be disregarded, as I got > confirmation that the server is indeed down ATM. > > Still wondering about the password, though, so.. anyone? :-) > > Regards, > Roger Kind Kristiansen > > > On 09/16/2011 03:16 PM, Roger Kristiansen wrote: >> Hi, >> >> First of all: I'm not sure if this is the correct mailing list for >> questions regarding the Database REST API. If it isn't then I'm sorry, >> and I hope you might point me in the right direction. >> >> I am in need of API access to the RIPE database, both for querying and >> updating. I have been looking at the REST API documented at >> http://labs.ripe.net/ripe-database/database-api/api-documentation. >> >> I can connect, but I am unable to get a response from the >> lab.db.ripe.net server. No error or anything else. I'm accessing the >> server from the address 193.69.55.146. >> >> Here's one example, using curl on one of your example URLs: >> >> $ curl -v http://lab.db.ripe.net/whois/lookup/ripe/mntner/RIPE-DBM-MNT >> * About to connect() to lab.db.ripe.net port 80 (#0) >> * Trying 193.0.19.31... connected >> * Connected to lab.db.ripe.net (193.0.19.31) port 80 (#0) >>> GET /whois/lookup/ripe/mntner/RIPE-DBM-MNT HTTP/1.1 >>> User-Agent: curl/7.21.3 (i686-pc-linux-gnu) libcurl/7.21.3 >> OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 >>> Host: lab.db.ripe.net >>> Accept: */* >>> >> >> .. then nothing. Anyone know what might be wrong here? >> >> Also I'm not quite sure where or how to get the required password to >> perform updates. Any pointers? Would be much appreciated. :-) >> >> >> Regards, >> Roger Kind Kristiansen >> > From roger.kristiansen at redpill-linpro.com Fri Sep 16 17:13:04 2011 From: roger.kristiansen at redpill-linpro.com (Roger Kristiansen) Date: Fri, 16 Sep 2011 17:13:04 +0200 Subject: REST API woes In-Reply-To: <4E736382.20602@ripe.net> References: <4E734C43.8030309@redpill-linpro.com> <4E735609.2020209@redpill-linpro.com> <4E736382.20602@ripe.net> Message-ID: <4E736780.5080500@redpill-linpro.com> Thanks Denis, I did notice this way of supplying passwords in the API documentation, but I have no idea what password I am supposed to supply or where that password will originate from..? This is prabably bleeding obvious to someone with any domain knowledge, which unfortunately I don't possess yet. Regards, Roger Kind Kristiansen On 09/16/2011 04:56 PM, Denis Walker wrote: > Dear Roger Kind Kristiansen, > > I am assuming your question is "how to get the required password 'into > the update engine' to perform updates?" > > Passwords are sent as HTTP parameters, for example > > https://lab.db.ripe.net/whois/modify///?password=... > > regards > Denis Walker > Business Analyst > RIPE NCC Database Group > > On 16/09/11:38 3:58 PM, Roger Kristiansen wrote: >> The first part of this question can be disregarded, as I got >> confirmation that the server is indeed down ATM. >> >> Still wondering about the password, though, so.. anyone? :-) >> >> Regards, >> Roger Kind Kristiansen >> >> >> On 09/16/2011 03:16 PM, Roger Kristiansen wrote: >>> Hi, >>> >>> First of all: I'm not sure if this is the correct mailing list for >>> questions regarding the Database REST API. If it isn't then I'm sorry, >>> and I hope you might point me in the right direction. >>> >>> I am in need of API access to the RIPE database, both for querying and >>> updating. I have been looking at the REST API documented at >>> http://labs.ripe.net/ripe-database/database-api/api-documentation. >>> >>> I can connect, but I am unable to get a response from the >>> lab.db.ripe.net server. No error or anything else. I'm accessing the >>> server from the address 193.69.55.146. >>> >>> Here's one example, using curl on one of your example URLs: >>> >>> $ curl -v http://lab.db.ripe.net/whois/lookup/ripe/mntner/RIPE-DBM-MNT >>> * About to connect() to lab.db.ripe.net port 80 (#0) >>> * Trying 193.0.19.31... connected >>> * Connected to lab.db.ripe.net (193.0.19.31) port 80 (#0) >>>> GET /whois/lookup/ripe/mntner/RIPE-DBM-MNT HTTP/1.1 >>>> User-Agent: curl/7.21.3 (i686-pc-linux-gnu) libcurl/7.21.3 >>> OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 >>>> Host: lab.db.ripe.net >>>> Accept: */* >>>> >>> >>> .. then nothing. Anyone know what might be wrong here? >>> >>> Also I'm not quite sure where or how to get the required password to >>> perform updates. Any pointers? Would be much appreciated. :-) >>> >>> >>> Regards, >>> Roger Kind Kristiansen >>> >> > From green at msu.ru Fri Sep 16 17:49:59 2011 From: green at msu.ru (Alexander Zubkov) Date: Fri, 16 Sep 2011 19:49:59 +0400 Subject: REST API woes In-Reply-To: <4E736780.5080500@redpill-linpro.com> References: <4E734C43.8030309@redpill-linpro.com> <4E735609.2020209@redpill-linpro.com> <4E736382.20602@ripe.net> <4E736780.5080500@redpill-linpro.com> Message-ID: <4E737027.5060508@msu.ru> On 09/16/2011 07:13 PM, Roger Kristiansen wrote: > Thanks Denis, > > I did notice this way of supplying passwords in the API documentation, > but I have no idea what password I am supposed to supply or where that > password will originate from..? Password is stored in maintainer object which is referenced by mnt-by field of object you willing to change. This described in more details somewhere in documentation of the RIPE database. > > This is prabably bleeding obvious to someone with any domain knowledge, > which unfortunately I don't possess yet. > > Regards, > Roger Kind Kristiansen > > > On 09/16/2011 04:56 PM, Denis Walker wrote: >> Dear Roger Kind Kristiansen, >> >> I am assuming your question is "how to get the required password 'into >> the update engine' to perform updates?" >> >> Passwords are sent as HTTP parameters, for example >> >> https://lab.db.ripe.net/whois/modify///?password=... >> >> regards >> Denis Walker >> Business Analyst >> RIPE NCC Database Group >> >> On 16/09/11:38 3:58 PM, Roger Kristiansen wrote: >>> The first part of this question can be disregarded, as I got >>> confirmation that the server is indeed down ATM. >>> >>> Still wondering about the password, though, so.. anyone? :-) >>> >>> Regards, >>> Roger Kind Kristiansen >>> >>> >>> On 09/16/2011 03:16 PM, Roger Kristiansen wrote: >>>> Hi, >>>> >>>> First of all: I'm not sure if this is the correct mailing list for >>>> questions regarding the Database REST API. If it isn't then I'm sorry, >>>> and I hope you might point me in the right direction. >>>> >>>> I am in need of API access to the RIPE database, both for querying and >>>> updating. I have been looking at the REST API documented at >>>> http://labs.ripe.net/ripe-database/database-api/api-documentation. >>>> >>>> I can connect, but I am unable to get a response from the >>>> lab.db.ripe.net server. No error or anything else. I'm accessing the >>>> server from the address 193.69.55.146. >>>> >>>> Here's one example, using curl on one of your example URLs: >>>> >>>> $ curl -v http://lab.db.ripe.net/whois/lookup/ripe/mntner/RIPE-DBM-MNT >>>> * About to connect() to lab.db.ripe.net port 80 (#0) >>>> * Trying 193.0.19.31... connected >>>> * Connected to lab.db.ripe.net (193.0.19.31) port 80 (#0) >>>>> GET /whois/lookup/ripe/mntner/RIPE-DBM-MNT HTTP/1.1 >>>>> User-Agent: curl/7.21.3 (i686-pc-linux-gnu) libcurl/7.21.3 >>>> OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 >>>>> Host: lab.db.ripe.net >>>>> Accept: */* >>>>> >>>> >>>> .. then nothing. Anyone know what might be wrong here? >>>> >>>> Also I'm not quite sure where or how to get the required password to >>>> perform updates. Any pointers? Would be much appreciated. :-) >>>> >>>> >>>> Regards, >>>> Roger Kind Kristiansen >>>> >>> >> > From roger.kristiansen at redpill-linpro.com Mon Sep 19 14:13:38 2011 From: roger.kristiansen at redpill-linpro.com (Roger Kristiansen) Date: Mon, 19 Sep 2011 14:13:38 +0200 Subject: REST API woes In-Reply-To: <4E737027.5060508@msu.ru> References: <4E734C43.8030309@redpill-linpro.com> <4E735609.2020209@redpill-linpro.com> <4E736382.20602@ripe.net> <4E736780.5080500@redpill-linpro.com> <4E737027.5060508@msu.ru> Message-ID: <4E7731F2.1080900@redpill-linpro.com> Thanks Alexander, I found this page which made things a bit clearer for me: https://www.ripe.net/data-tools/support/documentation/ripe-database-user-manual-getting-started Cheers, Roger On 09/16/2011 05:49 PM, Alexander Zubkov wrote: > On 09/16/2011 07:13 PM, Roger Kristiansen wrote: >> Thanks Denis, >> >> I did notice this way of supplying passwords in the API documentation, >> but I have no idea what password I am supposed to supply or where that >> password will originate from..? > > Password is stored in maintainer object which is referenced by mnt-by > field of object you willing to change. > This described in more details somewhere in documentation of the RIPE > database. > >> >> This is prabably bleeding obvious to someone with any domain knowledge, >> which unfortunately I don't possess yet. >> >> Regards, >> Roger Kind Kristiansen >> >> >> On 09/16/2011 04:56 PM, Denis Walker wrote: >>> Dear Roger Kind Kristiansen, >>> >>> I am assuming your question is "how to get the required password 'into >>> the update engine' to perform updates?" >>> >>> Passwords are sent as HTTP parameters, for example >>> >>> https://lab.db.ripe.net/whois/modify///?password=... >>> >>> >>> regards >>> Denis Walker >>> Business Analyst >>> RIPE NCC Database Group >>> >>> On 16/09/11:38 3:58 PM, Roger Kristiansen wrote: >>>> The first part of this question can be disregarded, as I got >>>> confirmation that the server is indeed down ATM. >>>> >>>> Still wondering about the password, though, so.. anyone? :-) >>>> >>>> Regards, >>>> Roger Kind Kristiansen >>>> >>>> >>>> On 09/16/2011 03:16 PM, Roger Kristiansen wrote: >>>>> Hi, >>>>> >>>>> First of all: I'm not sure if this is the correct mailing list for >>>>> questions regarding the Database REST API. If it isn't then I'm sorry, >>>>> and I hope you might point me in the right direction. >>>>> >>>>> I am in need of API access to the RIPE database, both for querying and >>>>> updating. I have been looking at the REST API documented at >>>>> http://labs.ripe.net/ripe-database/database-api/api-documentation. >>>>> >>>>> I can connect, but I am unable to get a response from the >>>>> lab.db.ripe.net server. No error or anything else. I'm accessing the >>>>> server from the address 193.69.55.146. >>>>> >>>>> Here's one example, using curl on one of your example URLs: >>>>> >>>>> $ curl -v http://lab.db.ripe.net/whois/lookup/ripe/mntner/RIPE-DBM-MNT >>>>> * About to connect() to lab.db.ripe.net port 80 (#0) >>>>> * Trying 193.0.19.31... connected >>>>> * Connected to lab.db.ripe.net (193.0.19.31) port 80 (#0) >>>>>> GET /whois/lookup/ripe/mntner/RIPE-DBM-MNT HTTP/1.1 >>>>>> User-Agent: curl/7.21.3 (i686-pc-linux-gnu) libcurl/7.21.3 >>>>> OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18 >>>>>> Host: lab.db.ripe.net >>>>>> Accept: */* >>>>>> >>>>> >>>>> .. then nothing. Anyone know what might be wrong here? >>>>> >>>>> Also I'm not quite sure where or how to get the required password to >>>>> perform updates. Any pointers? Would be much appreciated. :-) >>>>> >>>>> >>>>> Regards, >>>>> Roger Kind Kristiansen >>>>> >>>> >>> >> > > -- Roger Kristiansen Redpill Linpro AS - Changing the game Mobil: +47 917 88 471 From roger.kristiansen at redpill-linpro.com Mon Sep 19 14:29:29 2011 From: roger.kristiansen at redpill-linpro.com (Roger Kristiansen) Date: Mon, 19 Sep 2011 14:29:29 +0200 Subject: REST API on lab.db.ripe.net Message-ID: <4E7735A9.8030300@redpill-linpro.com> Is this API actually connected to the production database, or are the "test" and "ripe" sources it references only two different databases in a lab environment? Regards, Roger Kind Kristiansen From andy at nosignal.org Wed Sep 28 19:13:25 2011 From: andy at nosignal.org (Andy Davidson) Date: Wed, 28 Sep 2011 18:13:25 +0100 Subject: Building the software Message-ID: Hi, I've read the install procedures for the ripe whois database, and see that you mention you develop on Debian Linux. Can the pre-requisites be installed with packages, and do you have a list of packages I can paste into "dpkg --set-selections" to satisfy the pre-requisites ? I'll assume for now there is no package for the installed whois server.. :-) Andy