IETF Logo Mail Archive

RE: ietf.org unaccessible for Tor users

Ted Lemon <Ted.Lemon@nominum.com> Tue, 15 March 2016 11:44 UTC

Return-Path: <Ted.Lemon@nominum.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 8E3DA12D582 for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 04:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 G6IfZP4cr071 for <ietf@ietfa.amsl.com>; Tue, 15 Mar 2016 04:44:45 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80EA12D511 for <ietf@ietf.org>; Tue, 15 Mar 2016 04:44:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id AD9BE74002E; Tue, 15 Mar 2016 11:44:45 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-04.WIN.NOMINUM.COM ([64.89.235.67]) with mapi id 14.03.0224.002; Tue, 15 Mar 2016 04:44:45 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "cdel@firsthand.net" <cdel@firsthand.net>, Eliot Lear <lear@cisco.com>
Subject: RE: ietf.org unaccessible for Tor users
Thread-Topic: ietf.org unaccessible for Tor users
Thread-Index: AQHRfgKhUd2Ibe2Bf0ax7lfZ8xgy159aCzuAgACVPYCAAB/jgIAAAPcAgAACEID//54cD4AAdn8A//+Lr5A=
Date: Tue, 15 Mar 2016 11:44:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630797A3EF06@mbx-03.WIN.NOMINUM.COM>
References: <20160313143521.GC26841@Hirasawa> <m2a8m0y72q.wl%randy@psg.com> <F04B3B85-6B14-43BA-9A21-FC0A31E79065@piuha.net> <56E7E09D.7040100@cisco.com> <56E7E16C.4050803@firsthand.net> <56E7E327.2090803@cisco.com> <56E7F273.4030708@firsthand.net> <56E7F352.8050506@firsthand.net>,<56E7F470.1090104@cs.tcd.ie>
In-Reply-To: <56E7F470.1090104@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [71.233.41.235]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/xXE99ELtG5snNdiFlueR7ErVj5E>
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 11:44:47 -0000

The MiTM solution people are describing here seems like a very crude solution to this problem.   Perhaps the right way to address this problem is with less susceptible web server software, rather than with a privacy-destroying hack?

v2.23.0 | Report a Bug | By Email