Re: [saag] post-X509 cryptographic identities

Eric Rescorla <ekr@rtfm.com> Wed, 12 February 2020 01:17 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EE7120086 for <saag@ietfa.amsl.com>; Tue, 11 Feb 2020 17:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 wayMLqLPDPyI for <saag@ietfa.amsl.com>; Tue, 11 Feb 2020 17:17:04 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99B43120858 for <saag@ietf.org>; Tue, 11 Feb 2020 17:17:03 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id d10so316896ljl.9 for <saag@ietf.org>; Tue, 11 Feb 2020 17:17:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LLoh4TOR5Wgkgkge3T7B1Eov7gz0BXB9L02u2/I6oGs=; b=l3dYHF0vR1MiFiBLSFqYIxeYi7w1T/YJp1lQelinvvUsbyFoVPS6wbhMqwXJJVgO70 zTwl1wXxm28H9jPDhv/rQWwnVQXNXaL7YXBz2FihztsvdScaNVbvKO3iGF5qG5PuujFC O1CzpNp3ShjrsVI3zpq/3DwiiZs8TZQLlrUy4ULaW2EibIgny8BJxWnbzve50cWA3iQE CRpJT582uwtSnH3/aS3POKPE0E4G5PYdc5cd9VoKY17tKpEPz9UH6oYRnFmspUMLsX6J joNKMcdbRo/BbRqwjl8ObQTs+eDyLnJm7mO1EiTNYrjS1zNnAs0tm34l8hQ2e+oXQVyZ mv7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LLoh4TOR5Wgkgkge3T7B1Eov7gz0BXB9L02u2/I6oGs=; b=WI2nCXqs3wsjWB0EM8yF8+Boo6iFKxsWvZkSj9/TZuTawq/khazNyxoP0ie7mPN8rO uXBcxQx4k9ESGT2hxrSOxbOVJSopuCLBGWlI7q4qHt9g3sf5BQ7bdmhMhVHPVMKzhWyd sJ4viQYchYJEJsYR1dD9YiLI3ofc6OzmC9hipUismtHoXlzMz/DarJKsqfb1WSfX4EP5 8KDFwL7CSGuK3m94FNB+4Xl480bOJ/7RaeEM3h2lqhOOtmwVtImKMPTNIwLdMZbM3QvR B2DO24lJRBtvRIj+6nGU1ykhvSQ/RnkqbFTBWslLQYkKPalVrC/o3Wa8Ihll5XkVnpLH 4Dvw==
X-Gm-Message-State: APjAAAWv8d/iNQ3HfvHCDXuUDSE/1f43IoKujvRvQVTj2HyerBi53I8N 8SToqUMQUzuThJNtEUnxmHbLJOhAvhqi6o77wx79Ek7r
X-Google-Smtp-Source: APXvYqzkmZDM/W1T8YcSccJwdmi47U1g5uqEjT/I+yR+YOWMmQz5xiK2EEQ5rirRJvywQ+VMuLifNrZCN7JyvPtu78k=
X-Received: by 2002:a2e:b5a5:: with SMTP id f5mr5921075ljn.162.1581470221885; Tue, 11 Feb 2020 17:17:01 -0800 (PST)
MIME-Version: 1.0
References: <157762745765.1150.7880025422884493076@ietfa.amsl.com> <2C5DFA70-AD0E-4139-B28E-2D4EDB6E5409@sinodun.com> <46BDE9EB-6306-4194-AFFA-7E9E6604765F@sinodun.com> <825b8c8e-7ee9-9276-d09e-9c006acf3804@ericsson.com> <CABcZeBOzJ2MRS8deZqN+e-o9tFDwgSrYK3_hmV-0pfO+L9oaVw@mail.gmail.com> <53c87d6b-cad1-3a80-291d-e2a896705da5@ericsson.com> <CABcZeBNJWmFTV==6sa0qnAPyRr4=6OiCacchzobE=RozHnqPdg@mail.gmail.com> <7901248e-c7dd-8a12-65df-f40415fde5e2@cs.tcd.ie> <26497.1581418516@dooku> <db922345-12f5-33f6-2d85-01e858078ad7@cs.tcd.ie> <CABcZeBMR3KVunWGhm7BnX8KocUOuby1HecAatMFZy0acTxCO=g@mail.gmail.com> <3388d1ad-93f6-7d0d-3554-88ee67d1bb8b@cs.tcd.ie> <CABcZeBP4iVG8yeUVqjrDy25th-j0jJQAs1-z_NP0yGgOr21nfw@mail.gmail.com> <1dc76f29-a214-2172-fc4a-8a7262facdb4@cs.tcd.ie>
In-Reply-To: <1dc76f29-a214-2172-fc4a-8a7262facdb4@cs.tcd.ie>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 11 Feb 2020 17:16:25 -0800
Message-ID: <CABcZeBPn8RZ0QPgx8NvGiLxhx5hRP=UN03fUNwZpRvYjuduEUw@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, saag@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ccf9d2059e56bae3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/5G5ByoNqSp7s4lKGWcNaErgKTQw>
Subject: Re: [saag] post-X509 cryptographic identities
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Feb 2020 01:17:06 -0000

On Tue, Feb 11, 2020 at 5:09 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
>
> On 12/02/2020 00:51, Eric Rescorla wrote:
> > Well, I see what you say at the end, but I don't understand it. In TLS
> 1.3,
> > key establishment does not involve the cert, which is used for
> > authentication.
>
> Sure. And in a PQ world one might worry about factorisation
> and propose unwise changes to x.509 that involve >1 alg in
> the certificate signature and SPKI fields. My main point is
> that I think that'd be unwise. (Not so much because of TLS
> details, but more because of x.509 library details.)
>
> It'd be similarly unwise to want to try handle public keys
> for PQC KEMs via x.509 and given the entire world is not
> yet on TLS1.3, that'd maybe still be a bit of an issue.
>

Well, I don't think there is going to be much enthusiasm for adding PQ to
TLS 1.2, but even if there was, you would most likely do it the same way as
in 1.3, as a new DH "group"

-Ekr

Cheers,
> S.
>