[openpgp] Re: Specifying OpenPGP file extensions (and MIME type)?
Steffen Nurpmeso <steffen@sdaoden.eu> Thu, 19 December 2024 01:34 UTC
Return-Path: <steffen@sdaoden.eu>
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 D57C6C14F6FC for <openpgp@ietfa.amsl.com>; Wed, 18 Dec 2024 17:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 (2048-bit key) header.d=sdaoden.eu header.b="a2BOJgsq"; dkim=neutral reason="invalid (unsupported algorithm adaed25519-sha256)" header.d=sdaoden.eu header.b="wBrHD7Pb"
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 z2VsMOLVi2FF for <openpgp@ietfa.amsl.com>; Wed, 18 Dec 2024 17:34:54 -0800 (PST)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEEF9C14F6EC for <openpgp@ietf.org>; Wed, 18 Dec 2024 17:34:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1734572089; x=1735238755; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-author:resent-date:resent-from:resent-sender:resent-to: resent-cc:resent-reply-to:resent-message-id:in-reply-to:references: mime-version:content-type:content-transfer-encoding:content-disposition: content-id:content-description:message-id:mail-followup-to:openpgp: blahblahblah; bh=P1FWyLrLfpzkjPYJ7JKJQi99eh8N+js2/XKzGLwUXqg=; b=a2BOJgsqGqYstWM3PXnsN5h1cs8ghhu1yY0sFNofLsxKjPVbrksSl9/rdQcbEq+5wTzgCKPd UHtwG4w/Q8cwFI2nZfJsPFftMHBPGi6d2IB+xw9bKZs2Mkw/MpcbB2bnZ87X4oMCps75kCabyR OqwjtIkWDvMH7Fa+qyzZYwUS5K5JH7T8TLbHQuY+1+BG9EJWBZKGHhlEwyuu4EwPLFze4ek0/W zEOkW+5Uneg8SgAw80HvOtbgKdGUVuiZ68xLcEK2KQpqC8e6+2p4Fjt1pUp5Aw9IMkxggnJkkz pH2tClVPW+y2Y3ekxTj3GKy4E12s2/n9j7eawu2qvbIuktpw==
DKIM-Signature: v=1; a=adaed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1734572089; x=1735238755; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-author:resent-date:resent-from:resent-sender:resent-to: resent-cc:resent-reply-to:resent-message-id:in-reply-to:references: mime-version:content-type:content-transfer-encoding:content-disposition: content-id:content-description:message-id:mail-followup-to:openpgp: blahblahblah; bh=P1FWyLrLfpzkjPYJ7JKJQi99eh8N+js2/XKzGLwUXqg=; b=wBrHD7PbOEv70DR0lZjmsfLsjeR17taYxPV8eJR3ByHfTGC0pailOHlk5B/x4fu8dI7BtSN9 +92fYLCsaScCDw==
Date: Thu, 19 Dec 2024 02:34:47 +0100
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org>
Message-ID: <20241219013447.XP25ydfU@steffen%sdaoden.eu>
In-Reply-To: <Ts1QHIUYB28BAuFGcEAlziUv2P8z-9l3cvoIWqQP-LoGulOruNn15YUv1996s--1DZEm08nQZKwRoySSDxqzfkqW9FP1hL_nc0G9q3RE5pI=@protonmail.com>
References: <WKLyA6liA56T21xXuqMWjCP4K0eTEfOMuz8oNLua_JiZwEhJJiXjl9Ed7h-HrI_jUYeST-UJ-hEdOsaDjUeGBvvZZkewDRphetWVjCkICLc=@protonmail.com> <87y10efgxp.fsf@fifthhorseman.net> <sYcaYzsrk48hcbpG3CtdEreiML_V637bHCcmag-3ERtwt8l_LeC9LE40D6-8o_F7x5sPyhw-YpfZfzs9jj4wwHqKsPCd9HAXBvBbTj3dSVc=@protonmail.com> <C2AE8233-3509-4717-AEC1-B9102669EE65@andrewg.com> <Ts1QHIUYB28BAuFGcEAlziUv2P8z-9l3cvoIWqQP-LoGulOruNn15YUv1996s--1DZEm08nQZKwRoySSDxqzfkqW9FP1hL_nc0G9q3RE5pI=@protonmail.com>
Mail-Followup-To: Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org>, Andrew Gallagher <andrewg=40andrewg.com@dmarc.ietf.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, openpgp <openpgp@ietf.org>
User-Agent: s-nail v14.9.25-631-g1fab64ca11-dirty
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: S3YXGVYBTAK3XERKZCTZHUELBFM6LVP4
X-Message-ID-Hash: S3YXGVYBTAK3XERKZCTZHUELBFM6LVP4
X-MailFrom: steffen@sdaoden.eu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-openpgp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Andrew Gallagher <andrewg=40andrewg.com@dmarc.ietf.org>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, openpgp <openpgp@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: Specifying OpenPGP file extensions (and MIME type)?
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/qvN2MTACnN3v98aFOrKcR27C3yg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Owner: <mailto:openpgp-owner@ietf.org>
List-Post: <mailto:openpgp@ietf.org>
List-Subscribe: <mailto:openpgp-join@ietf.org>
List-Unsubscribe: <mailto:openpgp-leave@ietf.org>
Daniel Huigens wrote in <Ts1QHIUYB28BAuFGcEAlziUv2P8z-9l3cvoIWqQP-LoGulOruNn15YUv1996s--1DZEm08n\ QZKwRoySSDxqzfkqW9FP1hL_nc0G9q3RE5pI=@protonmail.com>: |On Wednesday, December 18th, 2024 at 16:42, Andrew Gallagher wrote: | |> I’d prefer to go in the other direction. Why do we have different \ |> grammars for messages and certificates? It prevents us from doing \ |> really simple stuff like appending a certificate to a message. If \ |> a message is a sequence of packets and a certificate is a sequence \ |> of packets - let’s just define an “OpenPGP packet sequence” and let \ |> the OpenPGP layer deal with the nuances of “message” vs “keyring” \ |> (certificate-ring?). | |Hmm. I'm not sure I agree; if you want to put a certificate in a message |then you can just do that, put the certificate inside the (encrypted/ |signed) message (e.g. as an attachment in the email context). |That seems cleaner to me. It is a good thing imho that you all do that now. IETF SML does not seem to fly, but in this hindsight an automatable solution appears attractive to me. Ie "a real autocrypt thing" in that i can take it for granted if a signed message includes such a part. (Ie it seems it cannot be as "hard" a relationship as with S/MIME and the extractable public key, but providing a "hard guarantee", isn't that desirable.) |There may be some sunk cost fallacy on my side as we spent a bunch of |effort in OpenPGP.js to make the parsing more strict / adhere to the |grammar more closely, e.g. `readMessage()` now throws if it includes a |key packet, and `readKey()` throws if it includes a data packet. While |this reduces flexibility in some sense, it also leads to better error |messages when you accidentally pass the wrong thing, for example. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) | |And in Fall, feel "The Dropbear Bard"s ball(s). | |The banded bear |without a care, |Banged on himself for e'er and e'er | |Farewell, dear collar bear
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Huigens
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Kahn Gillmor
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Huigens
- [openpgp] Re: Specifying OpenPGP file extensions … Andrew Gallagher
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Huigens
- [openpgp] Re: Specifying OpenPGP file extensions … Steffen Nurpmeso