Opened 7 years ago

Closed 2 years ago

#6695 closed enhancement (user disappeared)

add whois info

Reported by: cypherpunks Owned by: hellais
Priority: Low Milestone:
Component: Metrics/Onionoo Version:
Severity: Blocker Keywords:
Cc: nusenu@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Child Tickets

Change History (14)

comment:1 Changed 7 years ago by karsten

Sounds good. In fact, we already have whois information provided by Onionoo, but Atlas doesn't display it yet. Want to look at the other details that Onionoo provides and suggest which of them to add, and where? Want to submit a patch? :)

comment:2 in reply to:  1 ; Changed 7 years ago by cypherpunks

Replying to karsten:

Sounds good. In fact, we already have whois information provided by Onionoo, but Atlas doesn't display it yet.

I didn't find the whois information in the sample lookup URL you provided.

https://gitweb.torproject.org/onionoo.git/blob/HEAD:/DESIGN#l50

comment:3 in reply to:  2 ; Changed 7 years ago by karsten

Replying to cypherpunks:

I didn't find the whois information in the sample lookup URL you provided.

Ah, it's this line:

"host_name":"tor3.anonymizer.ccc.de",

https://gitweb.torproject.org/onionoo.git/blob/HEAD:/DESIGN#l57

comment:4 in reply to:  3 Changed 7 years ago by cypherpunks

Replying to karsten:

https://gitweb.torproject.org/onionoo.git/blob/HEAD:/DESIGN#l57

Reverse DNS lookup and a WHOIS record are two different things.

Reverse DNS record:

73.226.237.80.in-addr.arpa domain name pointer tor3.anonymizer.ccc.de

WHOIS record for 80.237.226.73:

inetnum:        80.237.226.72 - 80.237.226.79
netname:        DE-HEC-CCC
descr:          Chaos Computer Club e.V.
descr:          Mexikoring 21
descr:          22297 Hamburg
country:        DE
admin-c:        ANON-RIPE
tech-c:         CPA-RIPE
status:         ASSIGNED PA
remarks:        ---------------------------------
remarks:        This network is used for research
remarks:        in anonymisation services and
remarks:        provides a TOR exit node to end
remarks:        users.
remarks:        ---------------------------------
remarks:        Dieser Netzblock wird zur
remarks:        Erforschung von Anonymisierungs-
remarks:        techniken genutzt und stellt
remarks:        Endnutzern eine TOR-Instanz
remarks:        bereit.
remarks:        ---------------------------------
remarks:        https://www.ccc.de/anonymizer/
remarks:        ---------------------------------
mnt-by:         HOSTEUROPE-MNT
source:         RIPE # Filtered

person:         Julius Mittenzwei
address:        Chaos Computer Club e.V.
address:        Projektbetrieb Anonymizer
address:        Postfach 60 04 80
address:        22204 Hamburg
phone:          +49 40 401801-4500
fax-no:         +49 40 401801-55
nic-hdl:        ANON-RIPE
remarks:        ---------------------------------
remarks:        Addresses are solely for abuse
remarks:        handling purposes/Adressen sind
remarks:        nur fuer Missbrauchsmeldungen
remarks:        ---------------------------------
abuse-mailbox:  abuse@ccc.de
mnt-by:         CHAOS-MNT
source:         RIPE # Filtered

person:         Andreas Lehner
address:        Chaos Computer Club e.V.
address:        Projektbetrieb Anonymizer
address:        Postfach 60 04 80
address:        22204 Hamburg
phone:          +49 30 28097470-7723
fax-no:         +49 40 401801-55
nic-hdl:        CPA-RIPE
remarks:        ---------------------------------
remarks:        Technical contact only /
remarks:        Nur technische Anfragen
remarks:        ---------------------------------
abuse-mailbox:  abuse@ccc.de
mnt-by:         CHAOS-MNT
source:         RIPE # Filtered

% Information related to '80.237.128.0/17AS20773'

route:          80.237.128.0/17
descr:          DE-HEC-80-237-128
origin:         AS20773
member-of:      AS20773:RS-HOSTEUROPE
mnt-by:         HOSTEUROPE-MNT
source:         RIPE # Filtered

comment:5 Changed 7 years ago by karsten

Ah, we discussed adding whois record parts, but concluded that they're not standardized enough that we can grep single fields from all whois records of all relays out there. (We can't possibly include the whole record text). We decided to include reverse DNS lookup results and call it a day. Any reason to rethink that decision?

comment:6 Changed 7 years ago by cypherpunks

It is just a matter of convenience getting the whois record can be done with other methods but I find it useful to find out who or where a certain relay is running. WHOIS records usually give you more information than the AS info.

We can't possibly include the whole record text

As an option to solve the "space" problem you could include it and make it visible (expand) it after the user explicitly chooses to see it by clicking on "+" (like you frequently see on other pages). I would find this UI feature also useful for Exit Policy and MyFamily:
https://atlas.torproject.org/#details/7610BBD3F5BB67284EEE8476721AE6109DC29BEA

comment:7 in reply to:  6 Changed 7 years ago by karsten

Resolution: wontfix
Status: newclosed

Replying to cypherpunks:

It is just a matter of convenience getting the whois record can be done with other methods but I find it useful to find out who or where a certain relay is running. WHOIS records usually give you more information than the AS info.

We can't possibly include the whole record text

As an option to solve the "space" problem you could include it and make it visible (expand) it after the user explicitly chooses to see it by clicking on "+" (like you frequently see on other pages). I would find this UI feature also useful for Exit Policy and MyFamily:
https://atlas.torproject.org/#details/7610BBD3F5BB67284EEE8476721AE6109DC29BEA

The real space limitation isn't that Atlas couldn't display all the text, it's the number of bytes that full whois records would occupy in Onionoo's details documents. If there are single lines in whois records that we can reliably parse and add to details documents, I'd say let's do it. But adding the whole whois record is not an option.

Closing as wontfix.

comment:8 Changed 7 years ago by hellais

If there were a whois database that has a good API that we can interact with, then this may be doable.

comment:9 in reply to:  8 ; Changed 7 years ago by karsten

Resolution: wontfix
Status: closedreopened

Replying to hellais:

If there were a whois database that has a good API that we can interact with, then this may be doable.

I agree. Do you happen to know such a database and/or API that we could use?

comment:10 in reply to:  9 Changed 7 years ago by hellais

Replying to karsten:

Replying to hellais:

If there were a whois database that has a good API that we can interact with, then this may be doable.

I agree. Do you happen to know such a database and/or API that we could use?

ARIN appears to offer such a service: https://www.arin.net/resources/restful-interfaces.html.

Otherwise there are services that offer such a thing appear to be based on volume. For example this http://www.whoisxmlapi.com/ gives you for free the first 500 queries.

If we were to go for the later we would definitely need to store them somewhere.

I would first try and see how much data we can get out with the ARIN API and if we are breaching their TOS by doing one query per user.

If there are issues then we need to come up with something that stores the result of the queries, or at least caches them if we are interested in having such feature.

comment:11 Changed 7 years ago by karsten

I think it's a poor plan to have every Atlas request this information from some Internet service. We should rather look for something we can include in Onionoo's documents, so that Atlas users don't have to make additional request and so that other Onionoo clients can benefit from the added information, too. Ideally, we would download some blobs from ARIN and the four other registries once per day and have Onionoo extract the relevant parts from that.

Related to this ticket, I'm also interested in obtaining bulk whois information for improving Tor's internal GeoIP database (#6438).

comment:12 in reply to:  11 Changed 4 years ago by cypherpunks

Component: AtlasOnionoo
Priority: normalminor
Summary: add whois info to tor relay info pageadd whois info

Replying to karsten:

I think it's a poor plan to have every Atlas request this information from some Internet service. We should rather look for something we can include in Onionoo's documents, so that Atlas users don't have to make additional request and so that other Onionoo clients can benefit from the added information, too.

I also agree with that. So I change the component to to onionoo instead of atlas.

comment:13 Changed 4 years ago by tyseom

Cc: nusenu@… added

comment:14 Changed 2 years ago by iwakeh

Resolution: user disappeared
Severity: Blocker
Status: reopenedclosed

This ticket is more than two years w/o any changes.
Assuming it to be obsolete and closing.
Re-open, if necessary.

Note: See TracTickets for help on using tickets.