IETF Logo Mail Archive

Re: [openpgp] Transporting certificates in messages [was: Re: Transport public keys inside the message body]

Andrew Gallagher <andrewg@andrewg.com> Fri, 16 February 2024 14:35 UTC

Return-Path: <andrewg@andrewg.com>
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 23959C14F600 for <openpgp@ietfa.amsl.com>; Fri, 16 Feb 2024 06:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (2048-bit key) header.d=andrewg.com
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 iHhGUMx_rDvR for <openpgp@ietfa.amsl.com>; Fri, 16 Feb 2024 06:35:28 -0800 (PST)
Received: from fum.andrewg.com (fum.andrewg.com [135.181.198.78]) (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 D1FACC14F5F7 for <openpgp@ietf.org>; Fri, 16 Feb 2024 06:35:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=andrewg.com; s=andrewg-com; t=1708094124; bh=c4fQQzmu5pcrd/849Lc532+PW/TwuXfd8a+LRhUG6Lw=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=aPYmm/pf9afzmeVQbXUlRCZczAfsV9FiY01sYpkwowOlF5D/V1cxoc6ELCx4FZHxV dC7BcZpxy4vlyrB9xrWgIhmI+oehEziOj1nFYdV+AKvqodzdIvDDMw9njsVxCjYnMm xRvLv0OUJH3RC7uKZh1yqdd7+mcMzvxhae0M/KvxwpNwui6ol1ssIm3YsyvZ3SZPkC 2whPMhRkSLsoKkirzGuGmRLHyaML7FFWpWafBfJHG1iE4hlh/vOt3SX2H1iS6CW+sd cbfHxjg68SL+k6er2PDWBh5j9KRGb6H/d1ahyLwrORP7QH0mSdCWRHrPSk7VRFC29V ww2ZIFeTynmSg==
Received: from smtpclient.apple (serenity [IPv6:fc93:5820:7349:eda2:99a7::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by fum.andrewg.com (Postfix) with ESMTPSA id 8E4CD5DDE1; Fri, 16 Feb 2024 14:35:24 +0000 (UTC)
From: Andrew Gallagher <andrewg@andrewg.com>
Message-Id: <5558895E-3FE3-44A7-A2AC-3B904EA3BD53@andrewg.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4E01DC4A-911D-48B5-A2D8-348D56CA1F5F"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.1\))
Date: Fri, 16 Feb 2024 14:35:06 +0000
In-Reply-To: <c334a52d-d32c-4da1-992f-ca6062d35529@kuix.de>
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, "openpgp@ietf.org" <openpgp@ietf.org>
To: Kai Engert <kaie@kuix.de>
References: <33b847dd-2dfc-4741-a415-d4636642fef1@kuix.de> <87jzn52s5z.fsf@fifthhorseman.net> <f4db1928-4036-4b98-83b6-ca8af429a85e@kuix.de> <FD720EA6-B932-43F1-8ADD-FF7DC4EF1313@andrewg.com> <8BE5C271-1014-418C-9E39-EA7E6A321F7A@andrewg.com> <c334a52d-d32c-4da1-992f-ca6062d35529@kuix.de>
X-Mailer: Apple Mail (2.3731.700.6.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/6zOQd8R2aS7qqAty-GmCdE83akg>
Subject: Re: [openpgp] Transporting certificates in messages [was: Re: Transport public keys inside the message body]
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: Fri, 16 Feb 2024 14:35:32 -0000

On 16 Feb 2024, at 14:28, Kai Engert <kaie@kuix.de> wrote:
> 
> Do we have to strictly require that the outermost MIME part has a specific type, or can we just flexibly allow those extra MIME-part headers to be added to the outermost part, whatever type it might be?

I don’t know if it should be mandatory to use a particular outer MIME part, but it would be a good idea to test the alternatives and recommend one that minimises problems.

A

v2.46.0 | Report a Bug | By Email | System Status