Re: [openpgp] Reducing the meta-data leak
Daniel Kahn Gillmor <dkg@fifthhorseman.net> Tue, 05 January 2016 03:15 UTC
Return-Path: <dkg@fifthhorseman.net>
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 46D3E1ACEDF for <openpgp@ietfa.amsl.com>; Mon, 4 Jan 2016 19:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 ztryHL50I_A8 for <openpgp@ietfa.amsl.com>; Mon, 4 Jan 2016 19:15:41 -0800 (PST)
Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by ietfa.amsl.com (Postfix) with ESMTP id BD7A91ACEDD for <openpgp@ietf.org>; Mon, 4 Jan 2016 19:15:41 -0800 (PST)
Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 42242F989; Mon, 4 Jan 2016 22:15:38 -0500 (EST)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 947C620041; Mon, 4 Jan 2016 22:15:38 -0500 (EST)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Ben McGinnes <ben@adversary.org>, "Neal H. Walfield" <neal@walfield.org>, Derek Atkins <derek@ihtfp.com>
In-Reply-To: <568B1B25.7020202@adversary.org>
References: <87io5j764u.wl-neal@walfield.org> <sjm7flz9muf.fsf@securerf.ihtfp.org> <87h9l36tf1.wl-neal@walfield.org> <56874CB5.7060806@adversary.org> <87d1tgzwi0.fsf@alice.fifthhorseman.net> <568B1B25.7020202@adversary.org>
User-Agent: Notmuch/0.21+39~gd2ae295 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu)
Date: Mon, 04 Jan 2016 22:15:38 -0500
Message-ID: <87twmsyaw5.fsf@alice.fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/rS9Pdsmjjq4X2gPNyQk9DIF_21A>
Cc: IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] Reducing the meta-data leak
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: <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, 05 Jan 2016 03:15:43 -0000
On Mon 2016-01-04 20:23:49 -0500, Ben McGinnes wrote: >> Removing the metadata of who a message is for seems likely to require >> either: >> >> a) trial decryption on the recipient side (problematic for smartcard >> and multiple-secret-key setups, as Neal and Werner pointed out), or >> >> b) some sort of racheted shared state between sender and recipient >> (e.g. a briar- or axolotl-style esk, which might provide other nice >> features, like "deletable" ("forward-secret") messages) >> >> While (b) is out of scope for us here until we get 4880bis sorted, if >> someone wanted to experiment with that and report back, i'm sure it >> would be interesting to several people on the list. >> >> Or maybe there's a (c) option? > > There is, but I can't recall if I've mentioned it on this list or not, > but I know it's been mentioned on gnupg-users because that's how I > found out about it: > > http://www.confidantmail.org/ > > An attempt at side-stepping SMTP entirely and replacing the transport > method with one of the methods used by BitTorrent. It relies on GPG > for the message encryption and everything is contained within the > encrypted zip. The only addressing metadata is the key UID which is > of the format of: > > any-damn-thing-you-like@somehost-including-tor-hidden-sites-and-i2p-it-doesn't-care > > It even includes a clever means of achieving forward secrecy, but > arguably it could benefit from hiding the OpenPGP metadata a little > better. This sounds like an effort to hide the SMTP metadata, but doesn't involve hiding the metadata in the OpenPGP format itself. While i think this is a neat idea, i'm not convinced it's addressing the same problems that (a) and (b) are addressing. --dkg
- [openpgp] Reducing the meta-data leak Neal H. Walfield
- Re: [openpgp] Reducing the meta-data leak Tom Ritter
- Re: [openpgp] Reducing the meta-data leak Derek Atkins
- Re: [openpgp] Reducing the meta-data leak Neal H. Walfield
- Re: [openpgp] Reducing the meta-data leak Derek Atkins
- Re: [openpgp] Reducing the meta-data leak Ben McGinnes
- Re: [openpgp] Reducing the meta-data leak Daniel Kahn Gillmor
- Re: [openpgp] Reducing the meta-data leak Ben McGinnes
- Re: [openpgp] Reducing the meta-data leak Daniel Kahn Gillmor
- Re: [openpgp] Reducing the meta-data leak vedaal
- Re: [openpgp] Reducing the meta-data leak Daniel Kahn Gillmor