Re: [TLS] Update spec to match current practices for certificate chain order

Peter Gutmann <> Thu, 07 May 2015 14:20 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5B8A31A9004 for <>; Thu, 7 May 2015 07:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id A7plmH8dO370 for <>; Thu, 7 May 2015 07:20:25 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BA6B81A8A48 for <>; Thu, 7 May 2015 07:20:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=uoa; t=1431008419; x=1462544419; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=+t+BK45016c9arG/fcbxjqPFlPhBLeBJ3cCt+KkIjB0=; b=u72ham9uaCKI3npyr3qbNFGU5lMblfXPX6BZEYpdHax19hoVjRc6E6wS CuODX2MIEdZ7JjKWC4A80xSgOw01IUDsQwblwNAfuDQkOfTtwhwN87Yv+ pwC8gkIejf6/KS6VPqzXRd7c+oco9snbG/r/Q0FMlDdS4K4duIib9GFVT M=;
X-IronPort-AV: E=Sophos;i="5.13,384,1427713200"; d="scan'208";a="3542549"
X-Ironport-Source: - Outgoing - Outgoing
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 08 May 2015 02:20:18 +1200
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Fri, 8 May 2015 02:20:17 +1200
From: Peter Gutmann <>
To: "<>" <>
Thread-Topic: [TLS] Update spec to match current practices for certificate chain order
Thread-Index: AdCI0PBlwpfYkwi8TLGR/zDLR+HmmA==
Date: Thu, 7 May 2015 14:20:16 +0000
Message-ID: <>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [TLS] Update spec to match current practices for certificate chain order
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 May 2015 14:20:32 -0000

Martin Rex <> writes:
>Peter Gutmann wrote:
>> For example my code looks for a cert containing the site name
>> ("") and then builds a chain up via the parent links until it
>> can't find any more useful certs.  That just works no matter what the other
>> side sends.
>Adding workarounds for clearly bogus behaviour is a very bad strategy,
>because it makes the situation worse for everyone in the long run.

In my case (and possibly others) it's not a workaround since the same code
that does PKCS #7/CMS also does TLS cert chains, in order to handle the more
open-ended PKCS #7 requirements it automatically deals with oddball TLS