Re: [openpgp] [RFC4880bis PATCH] WIP: bind wire format representations to specific pubkey algorithms

Justus Winter <justus@sequoia-pgp.org> Wed, 09 June 2021 06:51 UTC

Return-Path: <justus@sequoia-pgp.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 213BB3A12D0 for <openpgp@ietfa.amsl.com>; Tue, 8 Jun 2021 23:51:39 -0700 (PDT)
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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 VW_Sj4uMz6kh for <openpgp@ietfa.amsl.com>; Tue, 8 Jun 2021 23:51:34 -0700 (PDT)
Received: from harrington.uberspace.de (harrington.uberspace.de [185.26.156.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 977163A12CD for <openpgp@ietf.org>; Tue, 8 Jun 2021 23:51:32 -0700 (PDT)
Received: (qmail 18450 invoked from network); 9 Jun 2021 06:51:26 -0000
Received: from localhost (HELO localhost) (127.0.0.1) by harrington.uberspace.de with SMTP; 9 Jun 2021 06:51:26 -0000
From: Justus Winter <justus@sequoia-pgp.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Florian Weimer <fw@deneb.enyo.de>
Cc: IETF OpenPGP WG <openpgp@ietf.org>
In-Reply-To: <87k0n7qb7c.fsf@fifthhorseman.net>
References: <20210602230847.3593022-1-dkg@fifthhorseman.net> <87eedg9u4d.fsf@mid.deneb.enyo.de> <871r9grzeb.fsf@fifthhorseman.net> <871r9g9nmr.fsf@mid.deneb.enyo.de> <87k0n7qb7c.fsf@fifthhorseman.net>
Date: Wed, 09 Jun 2021 08:51:24 +0200
Message-ID: <87y2bjv8cz.fsf@europ.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/JQkp6G-IrmxyvYyU_XtTaQEgYso>
Subject: Re: [openpgp] [RFC4880bis PATCH] WIP: bind wire format representations to specific pubkey algorithms
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2021 06:51:39 -0000

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> On Sat 2021-06-05 20:23:24 +0200, Florian Weimer wrote:
>> I guess every implementor who tries to layer OpenPGP on top of an
>> existing PKCS#1 implementation will eventually learn about this, but I
>> suspect I'm not the only one who was surprised by this.
>
> Good call, Florian.  Can you propose language that would clarify this in
> the current draft as implementation guidance?  seems like we might want
> guidance for both signature generation and verification.
>
> I've opened a request for a new test in the OpenPGP interoperability
> test suite to see whether any of the tested implementations can handle
> this:
>
> https://gitlab.com/sequoia-pgp/openpgp-interoperability-test-suite/-/issues/54

Seems all implementations handle this just fine:

  https://tests.sequoia-pgp.org/#Improbably_short_RSA_signatures

I also tested signatures that are not a multiple of 8 bits, same
picture.

Justus