[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #17297 [Tor Check]: TorCheck fails on new exit egress IP not in exit DB, confusing to users
#17297: TorCheck fails on new exit egress IP not in exit DB, confusing to users
-----------------------+-------------------------
Reporter: starlight | Owner: arlolra
Type: defect | Status: new
Priority: High | Milestone:
Component: Tor Check | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Sponsor: |
-----------------------+-------------------------
Changes (by starlight):
* priority: Medium => High
Comment:
This bug has a serious non-obvious impact that
potentially affects all Tor exit operators.
Due to exit-list inaccuracies, the popular SecToor list
operates a /24 DNSBL that some service providers use
for blocking access:
http://www.sectoor.de/tor.php#en-listed-net
This /24 list can cause operators difficulty
with their ISPs due to collateral damage to
other customers in the same address block
as their exit operates.
While it is obvious that service providers
should not use this list at all, it's also
obvious that not everyone engages common-sense
in such matters.
Removing the problem should make it possible
to convince SecToor to decommission the
netblock DNDBL.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17297#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs