Re: [openpgp] Weird OIDs in the 4880bis draft

Wiktor Kwapisiewicz <wiktor@metacode.biz> Wed, 15 February 2023 13:30 UTC

Return-Path: <wiktor@metacode.biz>
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 47DC2C165767 for <openpgp@ietfa.amsl.com>; Wed, 15 Feb 2023 05:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metacode.biz
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thEzelnPHt7O for <openpgp@ietfa.amsl.com>; Wed, 15 Feb 2023 05:30:24 -0800 (PST)
Received: from out-213.mta1.migadu.com (out-213.mta1.migadu.com [IPv6:2001:41d0:203:375::d5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D060C16950B for <openpgp@ietf.org>; Wed, 15 Feb 2023 05:30:24 -0800 (PST)
Message-ID: <ffba4699-63e5-2ec5-26a7-e4761ae9c9a7@metacode.biz>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metacode.biz; s=key1; t=1676467820; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0DqKv8Zc/7KAtFtlNha0RD7jAvBkK6O5RE2lNrkbgRA=; b=EnYcxdHh8pZevQEaVB8WVgGkyGPfRfjTzNKuxjgLQOsnog/sRo8kUA7X/rKPzFBtpIDYyc GGf+8jpl10OBFgeLqB6Pk1EhV0CXui8U2OdGq6wnvZ2/kMN2oSJhmdkeMSQkqMuHn0a3Jp beimPKqjKCM/Ple/4yNMMbCYTmch1iw=
Date: Wed, 15 Feb 2023 14:30:18 +0100
MIME-Version: 1.0
Content-Language: en-US, pl-PL
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
References: <SY4PR01MB6251EA22CEC03C5DCD203A0DEEA29@SY4PR01MB6251.ausprd01.prod.outlook.com> <5fa09b99-0e3f-6a1e-49b4-eebe7a08eccd@metacode.biz> <SY4PR01MB6251EA3D3FEAB9B1458AE9EBEEA29@SY4PR01MB6251.ausprd01.prod.outlook.com>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: Wiktor Kwapisiewicz <wiktor@metacode.biz>
Organization: Metacode
In-Reply-To: <SY4PR01MB6251EA3D3FEAB9B1458AE9EBEEA29@SY4PR01MB6251.ausprd01.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Migadu-Flow: FLOW_OUT
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/7lf_rf5If_zcddJwayxOAiZDCO8>
Subject: Re: [openpgp] Weird OIDs in the 4880bis draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
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, 15 Feb 2023 13:30:29 -0000

On 14.02.2023 14:32, Peter Gutmann wrote:
> Wiktor Kwapisiewicz <wiktor=40metacode.biz@dmarc.ietf.org> writes:
>> MPIs being counted in bits not bytes,
> That actually leads to an interesting point, I realise that the bit-lengths
> are too ingrained to change but just out of interest, is there any
> implementation that actually uses the bit lengths, as opposed to putting a * 8
> in every write and a / 8 in every read?

I'm not aware of any but I guess the fastest way to get answer to this 
question would be creating a test case here:
https://tests.sequoia-pgp.org/

MPI count is a rabbit-hole, e.g. the RFC says the count starts from the 
first bit set (1) so in theory the MPI could be padded (prefixed) with 
any number of clear (0) bits (or bytes):
   https://www.rfc-editor.org/rfc/rfc4880#section-3.2

If I'm reading the draft well it seems to be fixed in:
   https://openpgp-wg.gitlab.io/rfc4880bis/#section-3.2.1

"followed by the smallest series of octets that can represent the value 
while stripping off any leading zero octets".

But it seems this discussion has strayed a little bit too far from it's 
original goal ;)

Kind regards,
Wiktor