IETF Logo Mail Archive

Re: [openpgp] Encrypting / Signing the mail subject?

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 17 March 2015 00:48 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB061ACD8C for <openpgp@ietfa.amsl.com>; Mon, 16 Mar 2015 17:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 sbcFaaD3HBFf for <openpgp@ietfa.amsl.com>; Mon, 16 Mar 2015 17:48:50 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EEEF1A1BEC for <openpgp@ietf.org>; Mon, 16 Mar 2015 17:48:50 -0700 (PDT)
Received: by ladw1 with SMTP id w1so54453160lad.0 for <openpgp@ietf.org>; Mon, 16 Mar 2015 17:48:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=iUUCk1k4jI/rxqoGE9jOrMvpsZDLTtGjc1y0I2lA5FA=; b=v3sQo0Aa5KWaIpcqxuL6fYAqhIDOBFuDIYImQpzI+Kqm08LKECcw2uQuphge+BxtCR Gxg24nnnM8U/+UnmWj6RxC7ikquDycn9zZ1Dd4tbi+eAatz9MGCXSvjKxmRcU3FF1xNV eVx3mKzFPDus/obXWX4SxaX/VbwYNXacgQ5ly7JVXBwpBraavTfXD07UXsR32rrTJ63J YRgdolD7DjEkbVSBXfT9Kfh/lwUYkZh95gVJlooeo9SC/m1abnd1Uxhncl0ZWFSGihIr sXDXERDIE3EVV4S/uTxReEeaOT/dRRH+MNRlkfTQqNqR00Tn8P+Yb/0XyNOXqI4M0q/y CXBw==
MIME-Version: 1.0
X-Received: by 10.112.97.228 with SMTP id ed4mr43390242lbb.79.1426553329051; Mon, 16 Mar 2015 17:48:49 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.45.203 with HTTP; Mon, 16 Mar 2015 17:48:48 -0700 (PDT)
In-Reply-To: <87fv94r080.fsf@alice.fifthhorseman.net>
References: <87fv94r080.fsf@alice.fifthhorseman.net>
Date: Mon, 16 Mar 2015 20:48:48 -0400
X-Google-Sender-Auth: rgD355SwyjTZEZiQDhmrHXuZsp0
Message-ID: <CAMm+LwihnotXMGu+VE78gGNjZCiFFwSL2FB0-2J=gyOW_8cctQ@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: IETF OpenPGP <openpgp@ietf.org>
Content-Type: multipart/alternative; boundary="001a1133979a6e6e2d0511715480"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/5KVujmBunXdtxUTW8Xd371u773w>
Cc: gnupg-devel@gnupg.org, Albrecht Dreß <albrecht.dress@arcor.de>, Hanno Böck <hanno@hboeck.de>
Subject: Re: [openpgp] Encrypting / Signing the mail subject?
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 17 Mar 2015 00:48:52 -0000

On Mon, Mar 16, 2015 at 7:28 PM, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
wrote:

> Hi Albrecht--
>
> Sorry for the late followup -- this has now been raised on
> openpgp@ietf.org, so i'm moving the follow up there.
>
> On Sun 2015-02-22 13:14:36 -0500, Albrecht Dreß wrote:
> > I am currently working on the implementation of your proposal for Balsa
> [1], and would like to add a few comments.
>
> I'm glad to hear this!
>
> > Am 16.01.15 21:29 schrieb(en) Daniel Kahn Gillmor:
> >> PGP/MIME messages are the only reliably structured mail OpenPGP e-mail
> messages anyway [0].
> >
> > As your proposal is fully transparent, I think it could also be used
> > for RFC 2633 S/MIME (i.e. multipart/signed;
> > application/pkcs7-signature as well as for application/pkcs7-mime).
>
> yep, this seems correct to me, but i don't know enough about the S/MIME
> world to take the proposal there.  Maybe we should find some S/MIME
> folks to chime in on this.
>

I am not sure I am an S/MIME person. But I would like to see this sort of
problem fixed in decently layered fashion that allows the same approach to
be used in either.

SMTP and HTTP share a problem of mixing up routing information (From, To,
Path) and Content meta data. If we could untangle the two in a repeatable
fashion, we can use the same approach to encrypt stored data blobs.

So one approach would be to take the content-metadata headers out of the
STMP section of the message and push them into the body of the message.

That would then make possible approaches where the subject line is
encrypted under one key and the content payload is encrypted under another.

v2.23.0 | Report a Bug | By Email