Re: https at ietf.org

David Conrad <drc@virtualized.org> Thu, 07 November 2013 15:41 UTC

Return-Path: <drc@virtualized.org>
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 2F1DC21E819E for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 07:41:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KmwrQ5RnRGMy for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 07:40:56 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 6F42921E80B9 for <ietf@ietf.org>; Thu, 7 Nov 2013 07:40:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 21957862CB; Thu, 7 Nov 2013 10:40:53 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 36315-02; Thu, 7 Nov 2013 10:40:52 -0500 (EST)
Received: from [10.0.1.3] (dhcp-8c75.meeting.ietf.org [31.133.140.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 6B493862CA; Thu, 7 Nov 2013 10:40:52 -0500 (EST)
Subject: Re: https at ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: multipart/signed; boundary="Apple-Mail=_8D34EAD2-D81D-47B7-AE08-A9D475479E43"; protocol="application/pgp-signature"; micalg="pgp-sha1"
From: David Conrad <drc@virtualized.org>
X-Priority: 3
In-Reply-To: <055201cedbaa$412fd4a0$4001a8c0@gateway.2wire.net>
Date: Thu, 07 Nov 2013 07:40:51 -0800
Message-Id: <FDBF0362-7A2E-4D25-B42E-2BB2A3518B3F@virtualized.org>
References: <CAHBU6ivbrk=NXgd4_5Upik+8H0AbHRy3kJnN=8fcK+Bz3pOV9Q@mail.gmail.com> <alpine.LRH.2.01.1311051733570.4200@egate.xpasc.com> <01P0FR4HDQNG00004G@mauve.mrochek.com> <CAHBU6ivZS33r4HHbCC391Ug9fMtZkJ3nojEeeqH5L+0+o3ZqGQ@mail.gmail.com> <055201cedbaa$412fd4a0$4001a8c0@gateway.2wire.net>
To: "t.p." <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 07 Nov 2013 15:41:01 -0000

tp,

On Nov 7, 2013, at 3:12 AM, t.p. <daedulus@btconnect.com> wrote:
> For any https:// link, the initial html is downloaded, the CRL is
> downloaded and .....
> zilch, nothing, a blank screen and a little globe that spins for hours.
> 
> Quite what is wrong with the IETF certificate chain's CRL I do not know,
> but I do know that the IETF website is inaccessible with HTTPS.  

A good example of why we should eat our own dogfood, no?

Regards,
-drc