Opened 8 years ago
#994 closed defect (Fixed)
Tor check gives false negatives for exits that disallow port 80
| Reported by: | Sebastian | Owned by: | |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | Webpages/Website | Version: | 0.2.0.33 |
| Severity: | Keywords: | ||
| Cc: | Sebastian, karsten | Actual Points: | |
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
: karsten: that can't be the (only) bug. Remember that
email we got a while back? It claimed that tor.sebastianhahn.net wasn't an
exit, but it had been running (and been included in the consensus) for 40 days
: the reason for that was simple
: # Exit check to check.torproject.org or your exit checking website
: my $dstip = "209.237.247.217";
: my $dstport = 80;
: (and I just realized now)
: I don't exit to 80
: but check.tp.o tests whether you can exit to it on port 80
: So my node will always be a false negative
: That's clearly a bug in check
[Automatically added by flyspray2trac: Operating System: All]
Child Tickets
Change History (4)
comment:1 Changed 8 years ago by Sebastian
comment:2 Changed 8 years ago by Sebastian
hm. I quoted some old perl in the initial report, so that's not the culprit. The current python version works
comment:3 Changed 8 years ago by Sebastian
found the issue. fixed in 19608
comment:4 Changed 8 years ago by Sebastian
flyspray2trac: bug closed.
another thing:
: I just realized that check.torproject.org resolves to 209.237.247.84
for me. That is _not_ what is listed in the source.