> On 21 Mar 2016, at 08:51, grarpamp wrote:
>
>> I don't know of a CloudFlare website that blocks Tor entirely.
>
> Probably not possible thankfully because some exit IP's
> aren't readily passively / immediately identifiable as such.
> Censorship as policy is not winning proposition.
I meant
On 3/20/16, Tim Wilson-Brown - teor wrote:
>> On 21 Mar 2016, at 04:00, Philipp Winter wrote:
>>
>> Next, I ran the module for cloudflare.com, which does not seem to
>> whitelist Tor. 638 (75%) exit relays saw a CAPTCHA and 211 (25%)
>> didn't.
This roughly match my own deprecated tools, global
> On 21 Mar 2016, at 04:00, Philipp Winter wrote:
>
> I wrote an exitmap module [0] that can tell us how many exit relays see
> a CloudFlare CAPTCHA when connecting to a given site.
>
> First, I ran the module for coreos.com because it uses CloudFlare, but
> the owner configured it to whitelist
I wrote an exitmap module [0] that can tell us how many exit relays see
a CloudFlare CAPTCHA when connecting to a given site.
First, I ran the module for coreos.com because it uses CloudFlare, but
the owner configured it to whitelist Tor. Indeed, only one out of 864
exit relays saw a CAPTCHA: