Re: [lamps] Call for adoption of draft-vangeest-x509-hash-sigs-03

Adam Langley <agl@imperialviolet.org> Thu, 11 April 2019 19:00 UTC

Return-Path: <alangley@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44E53120726 for <spasm@ietfa.amsl.com>; Thu, 11 Apr 2019 12:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 pQ0fRV9kFoJk for <spasm@ietfa.amsl.com>; Thu, 11 Apr 2019 12:00:31 -0700 (PDT)
Received: from mail-qk1-f169.google.com (mail-qk1-f169.google.com [209.85.222.169]) (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 5FB1A1206DC for <spasm@ietf.org>; Thu, 11 Apr 2019 12:00:31 -0700 (PDT)
Received: by mail-qk1-f169.google.com with SMTP id s81so4138624qke.13 for <spasm@ietf.org>; Thu, 11 Apr 2019 12:00:31 -0700 (PDT)
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:content-transfer-encoding; bh=yPmwA/2KyuVF+ou8DoOw9n/NwRn2V5warKxJWblfd58=; b=Md/f4B+fXb4DSkd71Rah/a78MGdC8f19DIxbLrx1xdOZnsoKQjD0qqcekz73LgQykG bH2+RMxU2lno4YFM0GVnPWbl4crK2UQmYZrVsKUYBFPWmM/Pmi/BLFRmcHhGEdCepFLv y5S+FVIlCFr7nk+rqeyr6GNI3lWWWHPJ/1GEugQyQgE1cOUsnteYs+jdqUhAdmBEjCK+ 0uiQHVKPmdkTiQzSonkgGOl2CO+UvkhBBYNGzqC8d/MtaBtpVH/Vqj9EqIlFAUtPrLpO mnW6DFkTnE3/hu0k1lVSfnPRXmA1OvsC3uzPF+8+cnja17z8jaMtBN4M9+E3L0xM0TQh +Maw==
X-Gm-Message-State: APjAAAXjOQ5kg2FM1qoyA3hkOUscegqOMdVnqSeHhkymCoyUDSNAujBa hAjWwSOvgDaoBpzrI+rykkjbC7gidl28bBa4w34=
X-Google-Smtp-Source: APXvYqz7hdXSkOUO8Tne58twxadLdCAsUBJFaxQmMXQ3t2umZdIGjZvAyi4C9WTyPJUUWRX8B7bvEnxA9JQPaDxwuIs=
X-Received: by 2002:a37:9d06:: with SMTP id g6mr40556014qke.25.1555009230152; Thu, 11 Apr 2019 12:00:30 -0700 (PDT)
MIME-Version: 1.0
References: <BN6PR14MB1106140408FFB08553DEAE98835F0@BN6PR14MB1106.namprd14.prod.outlook.com> <D6AB5830-C69A-44CA-BD63-9B64F92C032E@vigilsec.com> <391B7EFF-C02D-4D2D-9C19-FA18B8F9FD6A@vigilsec.com>
In-Reply-To: <391B7EFF-C02D-4D2D-9C19-FA18B8F9FD6A@vigilsec.com>
From: Adam Langley <agl@imperialviolet.org>
Date: Thu, 11 Apr 2019 12:00:18 -0700
Message-ID: <CAMfhd9Vv6pm6XkMOWkwpg25EW_vCmYTFfFSybK4Wi1zvreVUGA@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: SPASM <spasm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/-XhH14xqq3Y7eEaE14G9NRbFf94>
Subject: Re: [lamps] Call for adoption of draft-vangeest-x509-hash-sigs-03
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 19:00:37 -0000

On Thu, Apr 11, 2019 at 11:31 AM Russ Housley <housley@vigilsec.com> wrote:
> We talked about the "Algorithm Identifiers for HSS and XMSS for Use in the Internet X.509 Public Key Infrastructure" <https://www.ietf.org/id/draft-vangeest-x509-hash-sigs-03.txt> document today dat the face-to-face meeting session.  It was suggested that the document is read for WG adoption.  Please voice your support or concerns on the list.

Since you're asking, my worries remain the same as outlined in
November[1] and thus I guess I'm "opposed", although that's a stronger
word that I would select.

There are firmware-signing contexts where size and verification speed
seem to preclude stateless signatures. There one may have to try and
invest in lots of infrastructure to manage the state. But such
contexts are also not using X.509 because of the same size concerns.

SPHINCS isn't an RFC, but it's perfectly sound as a basis for a
stateless signature scheme. (There are several, good, marginal
improvements in NIST submissions but they're not critical if rushing.)
I would go that route rather than throw a stateful primitive at
code-signing CAs and wishing them good luck.

[1] https://mailarchive.ietf.org/arch/msg/spasm/4EP3bX2adJBCmTjBMYazAKQJFU0


Cheers

AGL

--
Adam Langley agl@imperialviolet.org https://www.imperialviolet.org