IETF Logo Mail Archive

Re: [openpgp] Put Signature in an Email's Header

Wiktor Kwapisiewicz <wiktor@metacode.biz> Tue, 08 August 2023 10:25 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 13680C151552 for <openpgp@ietfa.amsl.com>; Tue, 8 Aug 2023 03:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 (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 xQRC9mEFGIcN for <openpgp@ietfa.amsl.com>; Tue, 8 Aug 2023 03:25:50 -0700 (PDT)
Received: from out-113.mta0.migadu.com (out-113.mta0.migadu.com [91.218.175.113]) (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 1FDB5C151074 for <openpgp@ietf.org>; Tue, 8 Aug 2023 03:25:49 -0700 (PDT)
Message-ID: <8d42f591-3aec-43c8-b476-abdafdb85dd7@metacode.biz>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metacode.biz; s=key1; t=1691490347; 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=bUPJOdz2eZikE+lzT57d9jQCmGewTiLEEiuRJO2LHVI=; b=L4IlFYwOGRRgE2B/0n7uoNM9vEfnXI+WZ2L/F+XwIU1OceIyKNkcRCZ/I0q00xJQoB7Ggz X0JeP/AWu0NYx5E6fLbi+qoFALVOd9NHUwp3BKoUEWxkdvUNszsNs3Tc11i65CFflt4OFn D2g1DB4EnrueqGC63zn7TaMaeKd0SUk=
Date: Tue, 08 Aug 2023 12:25:45 +0200
MIME-Version: 1.0
Content-Language: en-US, pl-PL
To: Werner Koch <wk@gnupg.org>
References: <48be3fcf-cdce-9ef4-655b-63b6dddf9310@kuix.de> <20201211095836.5218a72e@computer> <cd02d2db-0671-dfc0-dab3-dc793a2c1605@metacode.biz> <878sa4y7hy.wl-neal@walfield.org> <4dbaf770-2b2e-47cc-afb5-3ba07706aafd@kuix.de> <87a5v1j4xo.fsf@wheatstone.g10code.de> <db447915-fc25-4759-879e-b64020c0ec0e@kuix.de> <87zg31hoee.fsf@wheatstone.g10code.de> <ba560bb0-0fa5-40a2-b70d-83f36859e17e@metacode.biz> <87v8dphmec.fsf@wheatstone.g10code.de>
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: Wiktor Kwapisiewicz <wiktor@metacode.biz>
Organization: Metacode
Cc: openpgp@ietf.org, Kai Engert <kaie@kuix.de>
In-Reply-To: <87v8dphmec.fsf@wheatstone.g10code.de>
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/eiZkePyVzCLKK92GAhvlF5Z0JSM>
Subject: Re: [openpgp] Put Signature in an Email's Header
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: Tue, 08 Aug 2023 10:25:55 -0000

On 8.08.2023 12:13, Werner Koch wrote:> A signed mail with the signing 
key included (as done by CMS) is a
> straightforward way to bootstrap encrypted communication.  It is mail
> standards compliant and does not break when for example forwarding
> mails.

As far as I know (please correct me) there is no RFC number of the 
standard that specifies something like that for OpenPGP? (I mean 
"signing key included (as done by CMS)").

> You are tackling problems which have long been solved.

If by "have long been solved" you mean this:
https://www.ietf.org/archive/id/draft-koch-openpgp-2015-rfc4880bis-02.html#section-5.2.3.32 
then it's only a draft.

If Kai submits a draft of his own solution they'd be equal alternatives 
that can be considered by individual implementers.

Having been on the receiving end of the "no can do" advice with this 
mailing list not once, not twice I'd encourage Kai to try it out anyway 
and see the real-world impact of his solution first-hand.

Kind regards,
Wiktor

v2.23.0 | Report a Bug | By Email