Re: ietf.org unaccessible for Tor users

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 15 March 2016 14:02 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 058C712D5B8 for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 07:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 XwGCF8sjLJgr for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 07:02:00 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76A612DA4A for <ietf@ietf.org>; Tue, 15 Mar 2016 07:01:59 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2A2BC203AD; Tue, 15 Mar 2016 10:04:14 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9A83463755; Tue, 15 Mar 2016 10:01:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: ietf.org unaccessible for Tor users
In-Reply-To: <F04B3B85-6B14-43BA-9A21-FC0A31E79065@piuha.net>
References: <20160313143521.GC26841@Hirasawa> <m2a8m0y72q.wl%randy@psg.com> <F04B3B85-6B14-43BA-9A21-FC0A31E79065@piuha.net>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 15 Mar 2016 10:01:58 -0400
Message-ID: <26647.1458050518@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zDqBdlwKhPIYo-K6hb8m61VrXZs>
Cc: Yui Hirasawa <yui@cock.li>, IETF Disgust List <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 14:02:05 -0000

Jari Arkko <jari.arkko@piuha.net> wrote:
    > It is important that IETF documents are accessible via Tor. It is
    > important that whatever CAPTCHA's are being employed, they are
    > accessible to everyone. It is important that we at the IETF are able to
    > deal with DoS attacks.

These systems do not need to be the same system, do they?
I think we are talking about www.ietf.org, and not datatracker.

I think that most of www.ietf.org is static; that it could be rsync'ed, and
we could have instances (with different names) that aren't behind cloudflare
(but, which would be far more DDoS'able).

    > The question: Yui: I was under the (perhaps mistaken) assumption that
    > ietf.org is generally accessible to everyone in the usual way, but that
    > some blacklisted nodes will have to go through a CAPTCHA process before
    > being able to continue. Is this so, or is there an experience that says
    > nodes are blocked and there isn’t even a possibility to go through a
    > CAPTCHA? Or is the problem that there is a CAPTCHA but you do not feel
    > that it is done in a way that is appropriate? Does all this relate to
    > http or https traffic?

    > The observations:

    > o   I do not feel that contracted running of multiple copies of our
    > servers constitutes a man-in-the-middle arrangement.

    > o   I have asked the matter to be discussed in our IT/tools/IAOC
    > meetings, but I’ll note that we may not have any more magical answers
    > than what is already being discussed on the list.




--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-