IETF Logo Mail Archive

[openpgp] Re: Fwd: New Version Notification for draft-gallagher-email-invisible-signatures-00.txt

Andrew Gallagher <andrewg@andrewg.com> Thu, 08 May 2025 18:13 UTC

Return-Path: <andrewg@andrewg.com>
X-Original-To: openpgp@mail2.ietf.org
Delivered-To: openpgp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6E5952684B14 for <openpgp@mail2.ietf.org>; Thu, 8 May 2025 11:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=andrewg.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TE6HOQDfhEmK for <openpgp@mail2.ietf.org>; Thu, 8 May 2025 11:13:12 -0700 (PDT)
Received: from fum.andrewg.com (fum.andrewg.com [IPv6:2a01:4f9:c011:23ad::1]) (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 mail2.ietf.org (Postfix) with ESMTPS id AE2032684B0C for <openpgp@ietf.org>; Thu, 8 May 2025 11:13:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=andrewg.com; s=andrewg-com; t=1746727990; bh=qpo/tIReDpjj+/mTKP5yGI4TlVd0R7hXaKvhmDKTJO8=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=Rde+9BaDzsX1ksNoc1SWAAKfKl2ibza0Mw/aGzVHWSMF1QiUtxs+EV5Wx+TDNpllC syy/Ud9ErXiqtpqd4p/BRwqzbm781dXNDEFl+kxIeLJFI6b06hODYh+cavIucRIbiF ZXTZoGXJrk9cz3UReYrV5/Cgxq5vyiE7jOnl8wbWFw1lH88K772HIGlK1gxEEyITtI Vn1wXZ3DLT9BXNyVCyShVaVjyDxLJpRqnDWGBwZIb0vpk+7V86fdFybP+gW+ImZVGT rEgOj2oRtG2e5jnpo2+QqRXBydQ+TB95WdN8wetJir2md4HykjsZR1E8zIba0e74Rw zlnXn6CFzpzBg==
Received: from smtpclient.apple (unknown [176.61.115.103]) (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) (Client did not present a certificate) by fum.andrewg.com (Postfix) with ESMTPSA id 87C565EF8C; Thu, 8 May 2025 18:13:10 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Andrew Gallagher <andrewg@andrewg.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 08 May 2025 19:12:59 +0100
Message-Id: <A753FD3C-AF30-4F74-A5BE-D478C4E42D19@andrewg.com>
References: <20250508170548.g9NV9uDc@steffen%sdaoden.eu>
In-Reply-To: <20250508170548.g9NV9uDc@steffen%sdaoden.eu>
To: Steffen Nurpmeso <steffen@sdaoden.eu>
X-Mailer: iPhone Mail (22E252)
Message-ID-Hash: 662ZFPYQNDFWG7FVVKYKM6NOZULF2HNP
X-Message-ID-Hash: 662ZFPYQNDFWG7FVVKYKM6NOZULF2HNP
X-MailFrom: andrewg@andrewg.com
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: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, IETF OpenPGP WG <openpgp@ietf.org>, OpenPGP-based Email Encryption <openpgp-email@enigmail.net>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: Fwd: New Version Notification for draft-gallagher-email-invisible-signatures-00.txt
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/b1tYmzeBVh5upXw5ACxZNEsAlJA>
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>

On 8 May 2025, at 18:06, Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
> 
> (And moreover my real problem
> with the WG topic as such is that the public key cannot simply be
> extracted and saved and thereafter used, which one gets for free
> with S/MIME.  Maybe now with Sig: there will be a Sig: covered
> PKey: that can be used to verify Sig: as well as be saved?  That
> is cool.  With multipart/signed one needs to attach the key and
> then sign the whole thing, which makes for several parts which
> MUAs potentially can misunderstand.  Shall there be any.)

That’s what the autocrypt header is for. :-) It doesn’t matter whether the autocrypt header is signed over, because you can verify that the key made the signature.

A

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