Re: [Secdispatch] [EXTERNAL]Re: Can Composite sigs move back to LAMPS?

Eric Rescorla <ekr@rtfm.com> Sat, 18 January 2020 21:32 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ADE2120074 for <secdispatch@ietfa.amsl.com>; Sat, 18 Jan 2020 13:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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] 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 MRlCewY-pw1r for <secdispatch@ietfa.amsl.com>; Sat, 18 Jan 2020 13:32:01 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 41F23120019 for <secdispatch@ietf.org>; Sat, 18 Jan 2020 13:32:01 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id h23so30036548ljc.8 for <secdispatch@ietf.org>; Sat, 18 Jan 2020 13:32:01 -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=HMlFgVhBC5iVBRQlT8fuEYwHwdcxtUcmBZ46k8ZpzVc=; b=E+S/eU76KMlYcgbcMq2N+TYOqw8JuCGAZDO7yHEAosfULMvdWopuQEeSGZ33PnX+B1 0u7vM8ypAvaJKLeekNl/f6neeWjTnjMQ8EVYTk9MC6Xrw9sWwuZOIFVGYrRHKYNHziR7 C3gqP5D7isg8DSKNBvJ5OcdQHkMpvcsPupW+bhw8f708rPMSnDNw/Wb9kNu+aggos2Kj R46uPOUQpHXtRNOZCdxE/gw8dj97b9Vrv5hpo+ChJ7AcjKUD+niB5RsN6+NfkOCBrIQa HNM2RZPAH5cuwEzhjhUF6HfF9j+mM1qPzmd/wvODK9H/QVYkxVCDvjA9RKBNxBmVeUHB KOOg==
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=HMlFgVhBC5iVBRQlT8fuEYwHwdcxtUcmBZ46k8ZpzVc=; b=Nie8dHqU1sX7VCzu4gHRsJrw2sOyaujfEv5z5ByJ9ZNJFS9RIXmgZyL0E60qCZXPUD v4y0Dxx9bZxVAHcHB2B48nMfdoQufPVF0BG3djelmEsuCq5RRuT1ahIMkFRItTf9squS I/T6UZqM+b5LO2QwW5T2xhF0EyxOInNJTtr8RVHwpJX/2HsSJE3ehO8mpj+QH1jvWI9V HmUwqNQ92qgewhRxBdehlFnhfnuUP4y8acs8fYlq7+aWKOljnHxYQr6+Yno1gxeepVfn k3J+qlGB1VhlH+f4nCk+6OkBVrHHueNWERyldow7ttDjWFQkI4cPP7USm09N4dNAk5aM 98KQ==
X-Gm-Message-State: APjAAAXnZ5svc4XHqPpmg64LiW5dNuWPoieSgMu+fGP0/EcZ1J7tyqDU +gFDyDIPWzUy3k/SzvfWuE+ev7AFByJz1rtEgd5e+g==
X-Google-Smtp-Source: APXvYqyECaS9UjHfQhgfNf7dkaipgUWJc+Q1dgA3y6cyq44cWoJ1R7uCOQD9Wibq/ZBpFVAJqZU0h599B1ZPS3Lp3S0=
X-Received: by 2002:a2e:b0e3:: with SMTP id h3mr9151646ljl.56.1579383118998; Sat, 18 Jan 2020 13:31:58 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR11MB388377406A1AAEDCA397749C9B360@DM6PR11MB3883.namprd11.prod.outlook.com> <70b221bb-bc39-52cc-f9e0-a84261afe473@cs.tcd.ie> <09B0CA53-BAAF-4139-8179-2A70ADE58632@isara.com> <c0f620d7-4e22-18a5-c168-f66b737cae86@cs.tcd.ie> <CAPwdP4PG3i5-_BuVMdH0iMcJCT40xejoM=J3dH=pPO61T-F4Aw@mail.gmail.com> <3f9de00e-85ad-48ed-ba97-e1b5418e3867@cs.tcd.ie> <BYAPR11MB3478E8F964A34EDD232CFB03EE310@BYAPR11MB3478.namprd11.prod.outlook.com> <052d3ee0-41ae-c4f4-7013-6286942c468a@cs.tcd.ie> <DM6PR11MB3883DB8289E4EE1CDEFE7BA89B310@DM6PR11MB3883.namprd11.prod.outlook.com> <3140.1579364674@localhost> <CABcZeBPfGmnkDU-7ot43hC2E7XvB0XeAFFEmsST4S_Hk1GgOFg@mail.gmail.com> <15967.1579382030@localhost>
In-Reply-To: <15967.1579382030@localhost>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 18 Jan 2020 13:31:22 -0800
Message-ID: <CABcZeBMWu+Zd_+=gvcc328fm87B1RsxnUaH2HpYbp9Wv_OMUYQ@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IETF SecDispatch <secdispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c5c100059c70c90e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/G5SjljBa49mrOE1zFksdSi05XAY>
Subject: Re: [Secdispatch] [EXTERNAL]Re: Can Composite sigs move back to LAMPS?
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jan 2020 21:32:04 -0000

On Sat, Jan 18, 2020 at 1:13 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Eric Rescorla <ekr@rtfm.com> wrote:
>     mcr> In particular, it seems to me that we could add these multiple
>     mcr> entries to
>     mcr> certificates, using dummy algorithms, and test them in the field
>     mcr> against
>     mcr> existing browsers, web servers, IDS, firewalls, etc.
>
>     > It's not quite clear to me how this would work. As I understand it,
>     > this involves replacing the existing public keys and signatures, in
>     > which case they won't be acceptable to any Web browser (and you in
>     > fact won't be able to get BR-compliant certs)....
>
> No, it involves two sets of signatures.
> The traditional set and the new, yet-to-be-precisely-defined set.
>

Yes, but I had understood these tbe encoded on the wire as if they were a
new signature algorithm, with the result that such a certificate would not
be verifiable by an existing client.

Perhaps we should resolve this question first.

-Ekr





> It could be that CAFORUM rules would presently prevent these certificates
> From going into production, and during an experiment, that would be okay, I
> think.
>
> The reason to start this work now is to wring out the obsticales such as
> BR/CABFORUM rules that would prevent/slow-down adoption.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>