Opened 7 years ago

Closed 6 years ago

#7342 closed defect (fixed)

check.tpo erroneously asserts "Sorry. You are not using Tor."

Reported by: keb Owned by:
Priority: Medium Milestone:
Component: Applications/Tor Check Version:
Severity: Keywords:
Cc: arlolra Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Perhaps the website could be changed to add a footnote something like
"[*] In rare cases your exit node may use a secondary ip address or the exit relay may not be in the consensus. To be certain you are using Tor, click Torbutton and select New Identity, then refresh your browser."

example instance:
(2011-11-06 around 15h30 EDT)
Your IP address appears to be: 5.34.241.93

version TBB 0.2.2.39-5 x64 linux tarball

supplementary info from irc:
<dfly> keb: then your current exit uses one IP for the OR Port and one for outgoing connections most probably
<phobos> https://atlas.torproject.org/#search/5.34.241.93
<phobos> https://metrics.torproject.org/exonerator.html?targetaddr=&targetPort=&ip=5.34.241.93&timestamp=2012-11-05#relay
<arma> @source "5.34.241.93"
<arma> router Warlboro 5.34.241.111 9001 0 9030

Child Tickets

Change History (9)

comment:1 in reply to:  description Changed 7 years ago by arma

Replying to keb:

<arma> @source "5.34.241.93"
<arma> router Warlboro 5.34.241.111 9001 0 9030

Not that we should put much effort into anything that isn't "make TBB not reliant on some remote website being up and saying something", but to expand on my lines above: the directory authorities note what IP address uploaded a descriptor, and they see the descriptor before they put it in any votes or consensuses. So if we want to improve the Tor exitlist's response time, we could do it by exporting data from directory authorities.

comment:2 Changed 7 years ago by arma

Component: WebsiteTor Check

comment:3 Changed 6 years ago by arma

Cc: aagbsn phobos added

https://trac.torproject.org/projects/tor/ticket/9204#comment:5 gives a theory for why these false positives are showing up again.

Here's an interesting one:

arma@sergii$ ls -la /srv/tordnsel.torproject.org/state
total 232
drwxr-xr-x 2 tordnsel tordnsel   4096 Jul  4 22:03 .
drwxr-xr-x 9 tordnsel tordnsel   4096 Jun 18 15:36 ..
-rw-r--r-- 1 tordnsel tordnsel 171327 Jul  4 22:03 exit-addresses
-rw-r--r-- 1 tordnsel tordnsel  54946 Jul  4 22:45 exit-addresses.new

vs

arma@sergii$ ls -la /srv/tordnsel.torproject.org/srv/tordnsel.torproject.org/state/exit-addresses
-rw-r--r-- 1 tordnsel tordnsel 144104 Mar 14 09:29 /srv/tordnsel.torproject.org/srv/tordnsel.torproject.org/state/exit-addresses

I wonder which one is the "real" one.

comment:4 in reply to:  3 Changed 6 years ago by phobos

/srv/tordnsel.torproject.org/state is the real one. "Luke, read the code. Trust the force."

comment:5 Changed 6 years ago by mwolfe

Sorry. You are not using Tor.

Your IP address appears to be: 72.52.91.19

(NB: I checked by connecting to http://kpvz7ki2v5agwt35.onion/wiki/index.php/Main_Page
so 72.52.91.19 is a relay Tor uses but Torcheck doesn't seem to know about.)

comment:6 Changed 6 years ago by arma

Cc: arlolra added; aagbsn phobos removed

comment:7 in reply to:  5 Changed 6 years ago by arlolra

Replying to mwolfe:

Sorry. You are not using Tor.

Your IP address appears to be: 72.52.91.19

(NB: I checked by connecting to http://kpvz7ki2v5agwt35.onion/wiki/index.php/Main_Page
so 72.52.91.19 is a relay Tor uses but Torcheck doesn't seem to know about.)

Thanks for reporting. This is indeed a false negative that we're actively debugging.
(there's a few more listed here: https://github.com/arlolra/check/issues/21)

The issue for this particular relay is that TorDNSEL can't find it and the consensus has the wrong outbound address (72.52.91.30)
https://atlas.torproject.org/#details/BA998001D8F8E82EEFBDFA209EF57C0D6ED43F03

@arma: Is it reasonable to try and contact the owner to set the OutboundBindAddress?

comment:8 Changed 6 years ago by arlolra

Alright, check should be fixed for the exit node that mwolfe reported.
https://gitweb.torproject.org/check.git/commit/026e43b08656d78398b15742ddf510f6b17f859e

Did we want to say something like in the description?

"In rare cases your exit node may use a secondary ip address or the exit relay may not be in the consensus. To be certain you are using Tor, click Torbutton and select New Identity, then refresh your browser."

Otherwise I think we can close this till the next report.

Note: See TracTickets for help on using tickets.