Re: Proposed Statement on "HTTPS everywhere for the IETF"

Xiaoyin Liu <xiaoyin.l@outlook.com> Sun, 07 June 2015 03:08 UTC

Return-Path: <xiaoyin.l@outlook.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 641FB1A870E for <ietf@ietfa.amsl.com>; Sat, 6 Jun 2015 20:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.802
X-Spam-Level: *
X-Spam-Status: No, score=1.802 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 AFprDdhcz9Wa for <ietf@ietfa.amsl.com>; Sat, 6 Jun 2015 20:08:39 -0700 (PDT)
Received: from BAY004-OMC4S19.hotmail.com (bay004-omc4s19.hotmail.com [65.54.190.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D47F11A8700 for <ietf@ietf.org>; Sat, 6 Jun 2015 20:08:39 -0700 (PDT)
Received: from BAY180-W22 ([65.54.190.200]) by BAY004-OMC4S19.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sat, 6 Jun 2015 20:08:39 -0700
X-TMN: [W0kPO5kKSSn/W9AgBXO0hHzl8ix+fDD1]
X-Originating-Email: [xiaoyin.l@outlook.com]
Message-ID: <BAY180-W22CC446142733EDDCB5407FFB00@phx.gbl>
Content-Type: multipart/alternative; boundary="_ed771394-3d1c-4115-9dd5-79014a9143c6_"
From: Xiaoyin Liu <xiaoyin.l@outlook.com>
To: Hector Santos <hsantos@isdg.net>, Niels Dettenbach Syndicat.com <nd@syndicat.com>, Jari Arkko <jari.arkko@piuha.net>, IETF <ietf@ietf.org>
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
Date: Sat, 6 Jun 2015 23:08:39 -0400
Importance: Normal
In-Reply-To: <557310E6.4010109@isdg.net>
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com>, <CAL02cgRPFooA5fVFwvdprb3wPD+Y55pD+7RWjkACDv7T_TBW5Q@mail.gmail.com>, <1472054.O9DP0qoCQf@gongo> <556CBCF5.3060402@alvestrand.no>, <1C4D741C-89EA-4973-8536-D6A02EFD7624@syndicat.com>, <556D4C38.6060704@alvestrand.no>, <1F11D864-2532-4971-9771-F8037989A9BB@piuha.net>, <70AA892E-C97F-4EEA-9BB8-829F654FA57F@syndicat.com>, <557310E6.4010109@isdg.net>
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Jun 2015 03:08:39.0848 (UTC) FILETIME=[40BBFA80:01D0A0CF]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N5I2LsUgN48rD1b0XNXoIqoePZY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 07 Jun 2015 03:08:43 -0000

> Date: Sat, 6 Jun 2015 11:25:26 -0400
> From: hsantos@isdg.net
> To: nd@syndicat.com; jari.arkko@piuha.net; ietf@ietf.org
> Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
> 
> It could not update because the 
> HTTPS URL was failing due the browser seeing an erroneous "Invalid 
> Certificate" display with no option to accept, temporary or otherwise. 
>   You have to download via another browser that isn't so strict, yet.
 
Why does the IETF use invalid certificates in the first place? If this is due to a wrong system clock, then the user probably cannot visit Google, Facebook, GitHub, etc. as well, and at least Firefox and Chrome advise users to fix the clock in such situation.

Xiaoyin