Dear all,
By mistake I routed exit traffic from my Tor exit node through an IP that is used for NAT'ing where I live, for a short time. So now the NAT ip is found on https://check.torproject.org/exit-addresses which is a bit unfortunate, since cloudFlare now does CAPCHA check on my NAT traffic.
Is there a way to remove my NAT ip from the list of Tor exit nodes? The NAT address does not see any Tor traffic anymore.
Best regards, Paw
Hi,
Your IP leaves the official list of current Exits automatically when it ceases to be an Exit.
https://check.torproject.org/exit-addresses
However, it will remain on any web-blocking lists for as long as the web-blocking list operators please.
On the bright side you now have a daily reminder of the extent of Cloudflare's gigantic MitM business.
Cloudflare and their filthy ilk couldn't care less about the collateral damage they're inflicting on millions of people (as evidenced by their dishonest, stalling approach to the Tor-Captcha problem and the recent "cloudbleed" incident - and the very idea of selling MitM as a substitute of security in depth - is evidence enough that the whole operation is in bad faith).
The basic MO of their blocking lists: paint all traffic coming from one IP address with the same brush. Once something they deem "bad" comes from somewhere, use that as "ground truth" to "prove" that their "service" is useful.
https://blog.torproject.org/blog/trouble-cloudflare
Pure snake-oil. So why should they care for exactness? They just want to "make the web great again" for idiots by reducing the frequency of perceived "attacks", with minimal involvement or human effort.
So it wouldn't surprise me if Cloudflare won't unlist your IP on request because
a) apparently they don't think it worth their money to not piss off minorities such as Tor users and
b) you know, the "bad guys could do that too".
So maybe you'll have to route your home traffic through some VPN now to get around the Great Cloudwall.
But who knows.
Paw:
Dear all,
By mistake I routed exit traffic from my Tor exit node through an IP that is used for NAT'ing where I live, for a short time. So now the NAT ip is found on https://check.torproject.org/exit-addresses which is a bit unfortunate, since cloudFlare now does CAPCHA check on my NAT traffic.
Is there a way to remove my NAT ip from the list of Tor exit nodes? The NAT address does not see any Tor traffic anymore.
Best regards, Paw _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi again,
Paw:
Dear all,
By mistake I routed exit traffic from my Tor exit node through an IP that is used for NAT'ing where I live, for a short time. So now the NAT ip is found on https://check.torproject.org/exit-addresses which is a bit unfortunate, since cloudFlare now does CAPCHA check on my NAT traffic.
In the previous msg I just repeated the exit-addresses URL. I actually meant to ask: for how long has the Exit been offline? The oldest by LastStatus are now from 2017-03-01 ~15:00.
Is there a way to remove my NAT ip from the list of Tor exit nodes? The NAT address does not see any Tor traffic anymore.
Best regards, Paw _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Your IP leaves the official list of current Exits automatically when it ceases to be an Exit. In the previous msg I just repeated the exit-addresses URL. I actually meant to ask: for how long has the Exit been offline? The oldest by LastStatus are now from 2017-03-01 ~15:00.
You are right. The "wrong" exit node is not figuring on https://check.torproject.org/exit-addresses anymore. But it still visible from https://atlas.torproject.org/. Downtime 4 days 5 hours 21 minutes and 6 seconds Running false How long will it keep figuring on atlas?
So it wouldn't surprise me if Cloudflare won't unlist your IP on request
You are right. I have written some mails to support@cloudflare.com. According to https://support.cloudflare.com/hc/en-us/articles/203306930-Does-Cloudflare-b... Cloudflare updates its list of Tor exit node IP addresses every 15 minutes. But the reply I got from their support was:
it's not listed on honeypot it is not based on any maliscous activity but rather was a special list of TOR endpoints curated by the request of our customers to control access to their sites. As such your endpoint won't be removed from that as it is a TOR endpoint this is completely independent of the reputation.
They have not registered any malicious activity from the IP and it is not figuring on https://check.torproject.org/exit-addresses, but still they won't remove it from their list.
So maybe you'll have to route your home traffic through some VPN now to get around the Great Cloudwall.
I have a few extra IPs, so for now I am routing outbound http-traffic through one of them. But it is still a shame that such big companies can do as they like, without any means to correct mistakes.
Thank you for your reply.
Best, Paw
fnordomat fnordomat@posteo.net writes:
Hi again,
Paw:
Dear all,
By mistake I routed exit traffic from my Tor exit node through an IP that is used for NAT'ing where I live, for a short time. So now the NAT ip is found on https://check.torproject.org/exit-addresses which is a bit unfortunate, since cloudFlare now does CAPCHA check on my NAT traffic.
In the previous msg I just repeated the exit-addresses URL. I actually meant to ask: for how long has the Exit been offline? The oldest by LastStatus are now from 2017-03-01 ~15:00.
Is there a way to remove my NAT ip from the list of Tor exit nodes? The NAT address does not see any Tor traffic anymore.
Best regards, Paw _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
You are right. The "wrong" exit node is not figuring on https://check.torproject.org/exit-addresses anymore. But it still visible from https://atlas.torproject.org/. Downtime 4 days 5 hours 21 minutes and 6 seconds Running false How long will it keep figuring on atlas?
Atlas uses onionoo data. Onionoo data shows relays that were running at some point within the last 7 days.
tor-relays@lists.torproject.org
-
fnordomat -
nusenu -
Paw