Opened 3 years ago

Last modified 6 months ago

#20114 new defect

check.torproject.org false-negatives "not connected through tor"

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

Description

Tor Browser v6.0.4 on Linux reported that exiting via node 162.243.117.41 was "not connected through tor" on check.torproject.org

This seemed very odd, so we wanted to report it in case something anomalous is going on.

Child Tickets

Change History (10)

comment:1 Changed 3 years ago by cypherpunks

Component: - Select a componentApplications/Tor Check
Owner: set to arlolra

comment:2 Changed 3 years ago by gk

#20115 is a duplicate.

comment:3 Changed 3 years ago by arlolra

Thanks for reporting!

Atlas returns these two nodes for that IP,
https://atlas.torproject.org/#details/47BAD834309368640EA066913DF741AF413EDE5E
https://atlas.torproject.org/#details/C765F758204810421C1059FC182209569551609D

which is a family listening at the same IP.

The exit-addresses list shows,

ExitNode 47BAD834309368640EA066913DF741AF413EDE5E
Published 2016-09-11 03:57:56
LastStatus 2016-09-11 05:02:56
ExitAddress 89.187.142.208 2016-09-11 05:04:35
ExitAddress 178.20.55.16 2016-09-11 05:04:35
ExitAddress 62.149.25.15 2016-09-11 05:04:44

and

ExitNode C765F758204810421C1059FC182209569551609D
Published 2016-09-11 05:49:25
LastStatus 2016-09-11 07:02:56
ExitAddress 109.163.234.7 2016-09-10 21:10:57
ExitAddress 193.90.12.86 2016-09-10 21:11:22
ExitAddress 176.10.104.243 2016-09-11 06:06:07
ExitAddress 185.100.84.82 2016-09-11 07:13:46
ExitAddress 178.63.97.34 2016-09-11 07:13:47
ExitAddress 64.113.32.29 2016-09-11 07:14:11

All the addresses there belonging to other nodes on the list.

Clearly, TorDNSEL is buggy and maybe the family info here is a hint at the issue.

We've seen this before,
https://trac.torproject.org/projects/tor/ticket/10499#comment:3
https://trac.torproject.org/projects/tor/ticket/18078#comment:1

but now I've got something to go on.

comment:4 Changed 3 years ago by cypherpunks

Again today:

 Sorry. You are not using Tor.
Your IP address appears to be: 45.55.164.171

Known exits with this IP:
https://atlas.torproject.org/#details/D383A17C97EEA50B820FE0F5D60DA2D436535AE6
https://atlas.torproject.org/#details/FD5E1C921C2ED9A8428BBEED9179C6C8BB4E7E4A

comment:6 Changed 3 years ago by arlolra

Thanks for continuing to report.

I will carve out some time to look at this asap.

comment:7 Changed 2 years ago by cypherpunks

Summary: Tor Browser v6.0.4 on Linux reported that exiting via node 162.243.117.41 was "not connected through tor" on check.torproject.orgcheck.torproject.org false-negatives "not connected through tor"

comment:8 Changed 2 years ago by cypherpunks

#22161 closed as a duplicate

comment:9 Changed 2 years ago by cypherpunks

again:

Sorry. You are not using Tor.

Your IP address appears to be: 138.197.4.77

atlas sees two exits at that IP:
https://atlas.torproject.org/#search/138.197.4.77

comment:10 Changed 6 months ago by arlolra

Duplicate in #28824 for 107.178.36.26 and 178.63.97.34 in #23866

Note: See TracTickets for help on using tickets.