IETF Logo Mail Archive

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

Bart Butler <bartbutler@protonmail.com> Fri, 11 December 2020 12:19 UTC

Return-Path: <bartbutler@protonmail.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 9EB213A0B3B for <openpgp@ietfa.amsl.com>; Fri, 11 Dec 2020 04:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=protonmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id doPt5gVP15_c for <openpgp@ietfa.amsl.com>; Fri, 11 Dec 2020 04:19:40 -0800 (PST)
Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76E9F3A0B2E for <openpgp@ietf.org>; Fri, 11 Dec 2020 04:19:40 -0800 (PST)
Date: Fri, 11 Dec 2020 12:19:23 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1607689175; bh=LcKGIQFizxBZMuRpEIpPUp2vWXltnsbLMIznaUzRIqI=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=xP/+mK4v4BR3/qNuLgRF0U9h/0i42FLHj7z/89mZJ8SXfzKItv/it6yWU2dTF3nof vfXB/T+zQ29kZSPLIEC4MEoWJ4bTgpdGpnr5MXw9yuJQyr03/yz4YaI0Mo5CdhColU cgZKnwJT+UUyLIexgFJ+6LP/P/HPBcLnh+7spiZE=
To: Kai Engert <kaie@kuix.de>
From: Bart Butler <bartbutler@protonmail.com>
Cc: "Neal H. Walfield" <neal@walfield.org>, Wiktor Kwapisiewicz <wiktor=40metacode.biz@dmarc.ietf.org>, openpgp@ietf.org
Reply-To: Bart Butler <bartbutler@protonmail.com>
Message-ID: <vqoCUg721G-eauS6pfk-7eRNPP5S4PAgQmPuoPJ8mBqvSu9YKxZHPbSlQqV9l6SBhF6uJCzFej1GLZHQzRR3xnW8F4jbQACRIqO6lQYp18M=@protonmail.com>
In-Reply-To: <8dd0976f-f85d-66ed-489f-98fdacf8cf82@kuix.de>
References: <48be3fcf-cdce-9ef4-655b-63b6dddf9310@kuix.de> <20201211095836.5218a72e@computer> <cd02d2db-0671-dfc0-dab3-dc793a2c1605@metacode.biz> <878sa4y7hy.wl-neal@walfield.org> <8dd0976f-f85d-66ed-489f-98fdacf8cf82@kuix.de>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="---------------------1ae4f272ca51702403fcfbc13fb4a898"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/vgvI35ZwsaPeLLyc3cgKPB5xFZQ>
Subject: Re: [openpgp] Put Signature in an Email's Header
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Dec 2020 12:19:43 -0000

Hi Wiktor,

Does signature.asc even show up as an attachment if you set the disposition to inline for PGP/MIME? That would be the obvious solution for suppressing unwanted signature.asc attachments for non-aware recipients.

Bart

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, December 11th, 2020 at 11:22 AM, Kai Engert <kaie@kuix.de> wrote:

> On 11.12.20 11:14, Neal H. Walfield wrote:
> 

> > On Fri, 11 Dec 2020 10:03:44 +0100,
> > 

> > Wiktor Kwapisiewicz wrote:
> > 

> > > On 11.12.2020 09:58, Hanno Böck wrote:
> > > 

> > > > FWIW I have heard lots of complains about the signature attachment,
> > > > 

> > > > which is why I stopped sending signed emails by default a long time ago.
> > > 

> > > Too bad signatures cannot be put into headers (just like DKIM
> > > 

> > > signatures). That would not confuse people (because they generally
> > > 

> > > don't inspect headers) while providing necessary info for clients that
> > > 

> > > understand them.
> > 

> > When you say cannot, I think you mean there is no standard to so.
> > 

> > Technically, I think, it is possible, and it is a neat idea.
> 

> It's a nice idea, but it's also new, so it's not practical as the single
> 

> mechanism to use in the immediate future.
> 

> Preserving compatiblity with a majority of existing implementations is a
> 

> high priority for me, and using the gpg-keys attachment mechanism seems
> 

> best to achieve that.
> 

> Kai
> 

> openpgp mailing list
> 

> openpgp@ietf.org
> 

> https://www.ietf.org/mailman/listinfo/openpgp

v2.15.0 | Report a Bug | By Email