Re: ietf.org unaccessible for Tor users

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 16 March 2016 21:49 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 ED16C12D612 for <ietf@ietfa.amsl.com>; Wed, 16 Mar 2016 14:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 MYRWFBIbT3bV for <ietf@ietfa.amsl.com>; Wed, 16 Mar 2016 14:49:35 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31B6512D561 for <ietf@ietf.org>; Wed, 16 Mar 2016 14:49:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E8088BE58; Wed, 16 Mar 2016 21:49:33 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2-29fffXb8uP; Wed, 16 Mar 2016 21:49:32 +0000 (GMT)
Received: from [10.87.49.100] (unknown [86.42.16.188]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E60E3BE51; Wed, 16 Mar 2016 21:49:31 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1458164972; bh=iufMx3IJXJlMW57NDwk1ZhxVbTZ3FvpeNs4yE5JQmT0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=XczJ4F44yh+fR3BAcUCNznUQDTS8RO+otlL/js0NhE51RgeiXQT9mxcDrrEesLLq6 1oNaeYfZHRElcmihX/HIGfAcH6LEpmaPqMOeAbqLYC9QM/x4eNpdrOQfOhi07DWYZa MRVFq7j4w3ytZJnfacVRJI7b9s6I6Sukev1KBLsk=
Subject: Re: ietf.org unaccessible for Tor users
To: Michael StJohns <mstjohns@comcast.net>, Adam Roach <adam@nostrum.com>, ietf@ietf.org
References: <20160313143521.GC26841@Hirasawa> <m2a8m0y72q.wl%randy@psg.com> <F04B3B85-6B14-43BA-9A21-FC0A31E79065@piuha.net> <56E7E09D.7040100@cisco.com> <4349AFDD-350C-4217-9BEE-3DBD2F608F95@nohats.ca> <27177.1458050662@obiwan.sandelman.ca> <m2k2l3qud5.wl%randy@psg.com> <56E90304.3050407@cisco.com> <m2bn6eq59r.wl%randy@psg.com> <56E904A7.80200@cisco.com> <m2a8lyq4ud.wl%randy@psg.com> <56E90BF9.4090306@cisco.com> <56E9AC23.8060109@nostrum.com> <56E9B436.2090203@cisco.com> <56E9B543.9080000@nostrum.com> <56E9B5FF.1080301@cisco.com> <56E9B836.9080601@nostrum.com> <56E9C0CA.7040006@comcast.net> <56E9C258.7000108@nostrum.com> <56E9C6DE.6010807@comcast.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56E9D4EB.6030601@cs.tcd.ie>
Date: Wed, 16 Mar 2016 21:49:31 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56E9C6DE.6010807@comcast.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040505030103030607050702"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/f1ap4ngYYy5-lxPtT5qrXOfgHjo>
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: Wed, 16 Mar 2016 21:49:37 -0000

Mike,

On 16/03/16 20:49, Michael StJohns wrote:
> 
> Fair enough - so you're asking me to take it on faith that there is a
> real problem and that it effects sufficient numbers of folks that the
> IETF should spend *its* money and effort to fix? 

Did you miss the mail upthread where it was pointed out that
removing the restriction is a simple checkbox which I assume
costs no more money than we're giving CF already?

If we allow Tor access and that turns out to be a source of
problems, then I do think we ought re-evaluate, but I don't
think there's any cost here to the IETF to turn off the
restriction.

And to clarify another thing: this is not only about the captcha,
in testing today using TBB sometimes one gets access, sometimes
one gets a captcha and sometimes access is denied with no captca.
It seems to depend on the exit node IP.

Cheers,
S.