IETF Logo Mail Archive

Re: ietf.org unaccessible for Tor users

"John R Levine" <johnl@taugh.com> Tue, 15 March 2016 11:58 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 529F712D993 for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 04:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=J+qyH0dp; dkim=pass (1536-bit key) header.d=taugh.com header.b=UAzO+1Bl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PULyYbBsXRTw for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 04:58:07 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7213812D98F for <ietf@ietf.org>; Tue, 15 Mar 2016 04:58:07 -0700 (PDT)
Received: (qmail 70170 invoked from network); 15 Mar 2016 11:58:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=11219.56e7f8cd.k1603; bh=qJ2OhoIx68Qbqhxas6wbRzbgVGUNWdeMTRn84xRE48Y=; b=J+qyH0dpyWpcTbabC/u59xSJ6UTheDFJ+i8+pqrE6G31GBnK97K2GfMnJaFrzxuirvWC2WbKqfCdOa11cxMDy2gRes3sYwV+352wWEuMg6sRE5tXIxCQnEgrDNDv1kbjvI2AeAYFi6u/ZHli9HZC006H/1LTqSepWrvXbdzEow8vm27royYPkgDjK5ABMTR/k7pWgvQt34hyNLY3bXpbU8OCzsk2KHhTMbvAX8/Wi6UAmpuUnwqkc+fxEGWxNXC/
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=11219.56e7f8cd.k1603; bh=qJ2OhoIx68Qbqhxas6wbRzbgVGUNWdeMTRn84xRE48Y=; b=UAzO+1BlNSYNKe3uslFjzbN9StK/uZsyQP/pb9EKp/7+80Hrel43ck/51EGmz7TAtRK7IMuiA40kGsbxJqYAgXAw0Hq3xqnDC3bTVfWSHzHfu8du8Q3SexG3JRIlcC1ZO9HeV643IjR/cqn3Aq+03BuwEdFuESV/bzh9d1rA49QcsyDEYso0igp1J2HB4UBDLTAd+C7X61MQZCBteYXJAqBiMf8CvUssS+KMdSJxRkwXx4FIR15g3mEpyCGm/gYl
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 15 Mar 2016 11:58:05 -0000
Date: Tue, 15 Mar 2016 07:58:04 -0400
Message-ID: <alpine.OSX.2.11.1603150755160.47203@ary.lan>
From: John R Levine <johnl@taugh.com>
To: Narelle <narellec@gmail.com>
Subject: Re: ietf.org unaccessible for Tor users
In-Reply-To: <CACRMD1Gp_3xjanC+YXLrwo9FMcDay1JQ6YPtAS1tTqk+C_AUVg@mail.gmail.com>
References: <m2a8m0y72q.wl%randy@psg.com> <20160315002604.15726.qmail@ary.lan> <CACRMD1Gp_3xjanC+YXLrwo9FMcDay1JQ6YPtAS1tTqk+C_AUVg@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SJlg0nQUDBbEEf3H8sZ_OBVI5ek>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2016 11:58:09 -0000

>> In article <m2a8m0y72q.wl%randy@psg.com> you write:
>>>> By using CloudFlare IETF is actively blocking Tor connections to IETF
>>>> page.
>>
>> Only if you're a robot that can't do the captcha.
>
> I haven't checked this particular captcha but ...
>
> Google has adopted 'reCaptcha' which seems to pass the accessibility
> requirements for most of the vision impaired people we work with.

So does Cloudmark.  You can see an example here:

https://support.cloudflare.com/hc/en-us/articles/203306930-Does-CloudFlare-block-Tor-

For all its noble intentions, most of the traffic that comes out of Tor is 
malicious.  (Any service that is anonymous and free has the same 
problems.)  Cloudmark and other providers don't block or filter it for 
political reasons, they do so to protect their users.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email