1,019 karma · joined December 19, 2017
contact: hn@tuxli.ch
I've just added it to my firewall that does around 160Mbit/s right now using an ipset and the only increase in CPU I can see is a small blip from the ipset restore. And that's just an APU2 with a AMD GX-412TC (1GHz Quad core from 2014) and not a beefy box.
Alt227 has a point but the Tor network is centered around a handful countries where traffic is cheap and there aren't that many huge IXs and Tier 1 ISPs where much of the traffic flows through.
I'm not saying that this is done but it's IMHO more likely than state actors running thousands of relays.
[bauruine@tp:projects/misc]$ python check_ip_tor.py /tmp/malicious_ips.txt
Got a total of 6303 malicious IPs
Of which 15 are Tor relays
Edit: Small addendum here are the worst 5 ASNs. 1607 TENCENT-NET-AP-CN
738 DIGITALOCEAN-ASN
483 KIXS-AS-KR
205 GOOGLE-CLOUD-PLATFORM
115 OVHGovernments have other possibilities. Why should they run a relay if they can force the ISP to mirror the traffic of all relays to them?
Why do you think your IPv7 will magically just work? There will be problems with it and IT departements will still disable it.
[0]: https://community.torproject.org/relay/setup/webtunnel/
https://gitlab.torproject.org/tpo/applications/tor-browser/-...
Something like this [0] where they try to contact you by phone and snail mail and keep your stuff online for more than half a year even if you don't pay is a paid exception and not the norm.
No it's not a list of exits but a list of ALL Tor relays. Please don't use this there is an official list [0] just use that if you need to.
Maybe the others are better maintained but this leaves a very bad impression.
>AS397702 1776 Solutions
Nice virtue signaling. This list is described as opionated so I guess it's fine.
I know you can do address harvesting like it was done with pool.ntp.org by shodan but if you don't use any public services your IoT devices are basically protected by the 128bit address space. So you need a address harvesting possibility, and people are watching for this as seen in the shodan case, and an exploitable issue at the same time. Not impossible and you should use a firewall but orders of magnitude less scary than a public routable IPv4 address.
I wonder how Diversion handles operations that possibly delete data. Whats their solution?