Re: [TLS] Key agility issue in draft-ietf-tls-subcerts?

Ilari Liusvaara <ilariliusvaara@welho.com> Fri, 06 July 2018 05:35 UTC

Return-Path: <ilariliusvaara@welho.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D924130DE2 for <tls@ietfa.amsl.com>; Thu, 5 Jul 2018 22:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 etUZDalpZJAt for <tls@ietfa.amsl.com>; Thu, 5 Jul 2018 22:35:51 -0700 (PDT)
Received: from welho-filter4.welho.com (welho-filter4.welho.com [83.102.41.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99AEB130DD0 for <tls@ietf.org>; Thu, 5 Jul 2018 22:35:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by welho-filter4.welho.com (Postfix) with ESMTP id DD0BE4F914; Fri, 6 Jul 2018 08:35:48 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp1.welho.com ([IPv6:::ffff:83.102.41.84]) by localhost (welho-filter4.welho.com [::ffff:83.102.41.26]) (amavisd-new, port 10024) with ESMTP id 7Oexel5kWXdZ; Fri, 6 Jul 2018 08:35:48 +0300 (EEST)
Received: from LK-Perkele-VII (87-92-19-27.bb.dnainternet.fi [87.92.19.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp1.welho.com (Postfix) with ESMTPSA id 5B570286; Fri, 6 Jul 2018 08:35:46 +0300 (EEST)
Date: Fri, 06 Jul 2018 08:34:09 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: "Patton,Christopher J" <cjpatton@ufl.edu>
Cc: "tls@ietf.org" <tls@ietf.org>
Message-ID: <20180706053409.GA26239@LK-Perkele-VII>
References: <MWHPR22MB0461699E06FBD28ECF75B276C6470@MWHPR22MB0461.namprd22.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <MWHPR22MB0461699E06FBD28ECF75B276C6470@MWHPR22MB0461.namprd22.prod.outlook.com>
User-Agent: Mutt/1.10.0 (2018-05-17)
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/N4TGthQUSldxfbLClROF4ho-cZE>
Subject: Re: [TLS] Key agility issue in draft-ietf-tls-subcerts?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2018 05:35:55 -0000

On Fri, Jul 06, 2018 at 01:11:34AM +0000, Patton,Christopher J wrote:
> The string over which the delegation signature is computed contains
> the `SubjectPublicKeyInfo` of the DC public key. This in turn
> contains an `AlgorithmIdentifier`. Does an X.509 `AlgorithmIdentifier`
> determine a unique TLS `SignatureScheme`?

Unfortunately not. While the ECDSA and EdDSA keys indeed only have one
valid SignatureScheme, RSA keys have three (the difference being
using SHA-256 vs. SHA-384 vs. SHA-512). This holds for both genric
RSA keys and RSA-PSS keys (and the signatureschemes are different for
those two).

Also, relying on this even for ECDSA keys might not be a good idea,
as if another hash ever gets added, then there could be mulitple
SignatureSchemes even for ECDSA keys.


-Ilari