Re: [lamps] Draft addition of header protection to the LAMPS charter

Hernâni Marques (p≡p project) <hernani@pep-project.org> Fri, 11 January 2019 19:39 UTC

Return-Path: <hernani@pep-project.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F56912870E for <spasm@ietfa.amsl.com>; Fri, 11 Jan 2019 11:39:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level:
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
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 XuQM0o6ALvM0 for <spasm@ietfa.amsl.com>; Fri, 11 Jan 2019 11:39:53 -0800 (PST)
Received: from dragon.pibit.ch (dragon.pibit.ch [94.231.81.244]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E3C6127AC2 for <spasm@ietf.org>; Fri, 11 Jan 2019 11:39:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by dragon.pibit.ch (Postfix) with ESMTP id B0DD8171C069; Fri, 11 Jan 2019 20:39:49 +0100 (CET)
Received: from dragon.pibit.ch ([127.0.0.1]) by localhost (dragon.pibit.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b4GzPRRikxav; Fri, 11 Jan 2019 20:39:47 +0100 (CET)
Received: from [192.168.43.199] (0.229.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch [178.197.229.0]) by dragon.pibit.ch (Postfix) with ESMTPSA id 62CF7171C05E; Fri, 11 Jan 2019 20:39:47 +0100 (CET)
To: spasm@ietf.org, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Russ Housley <housley@vigilsec.com>
References: <DC188C55-6FDE-4E64-9151-54815E96B50B@vigilsec.com> <87bm5hxdn0.fsf@fifthhorseman.net> <1194C123-1234-4B86-8EC1-26CE577CAFDA@vigilsec.com> <BB06AD4F-5F6F-4986-9ADC-04B44E34D0DE@vigilsec.com> <87imyvcb3m.fsf@fifthhorseman.net> <7DC69A08-3A4E-4D57-B490-179B8E4A411E@vigilsec.com>
From: "Hernâni Marques (p≡p project)" <hernani@pep-project.org>
Openpgp: preference=signencrypt
Message-ID: <0319e3b2-81b7-13af-df9e-436a15ee1074@pep-project.org>
Date: Fri, 11 Jan 2019 20:39:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <7DC69A08-3A4E-4D57-B490-179B8E4A411E@vigilsec.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="xa99I1ZUa8pPV2W78rGnnFIwmlrSdFiZl"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/HgCvnaaIOBQh5SkQk_8FgG03eaM>
Subject: Re: [lamps] Draft addition of header protection to the LAMPS charter
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2019 19:39:55 -0000

Hello dkg & Russ & list

On 11.01.19 19:56, Russ Housley wrote:

> --- BEGIN DKG-2 ---
> 
> 7. Update the specification for the cryptographic protection of e-mail
> headers - both for signatures and encryption - to improve the
> implementation situation with respect to privacy, security and usability
> in cryptographically-protected electronic mail.  Most current
> implementations of cryptographically-protected electronic mail protect
> only the body of the message, which leaves significant room for attacks
> against otherwise-protected messages.
> 
> --- END DKG-2 ---

Thanks for the new suggestion!

Despite *email, I can live with that, but if there's no objection I
would also add interoperability to the list, such as to have the
following text:

--- BEGIN HM-1 ---

7. Update the specification for the cryptographic protection of email
headers -- both for signatures and encryption -- to improve the
implementation situation with respect to privacy, security, usability
and interoperability in cryptographically-protected electronic mail.
Most current implementations of cryptographically-protected electronic
mail protect only the body of the message, which leaves significant room
for attacks against otherwise-protected messages.

--- END HM-1 ---

Greets!