Re: [Endymail] Off we go...

Werner Koch <wk@gnupg.org> Mon, 01 September 2014 10:16 UTC

Return-Path: <wk@gnupg.org>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C29B71A031F for <endymail@ietfa.amsl.com>; Mon, 1 Sep 2014 03:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5] 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 Gr6V8MNcZZXi for <endymail@ietfa.amsl.com>; Mon, 1 Sep 2014 03:16:44 -0700 (PDT)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [217.69.77.222]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A965A1A0282 for <endymail@ietf.org>; Mon, 1 Sep 2014 03:16:44 -0700 (PDT)
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.80 #2 (Debian)) id 1XOOfC-0002gj-Ho for <endymail@ietf.org>; Mon, 01 Sep 2014 12:16:42 +0200
Received: from wk by vigenere.g10code.de with local (Exim 4.82 #3 (Debian)) id 1XOOZw-0004Pq-8a; Mon, 01 Sep 2014 12:11:16 +0200
From: Werner Koch <wk@gnupg.org>
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <53FD0B7D.8070705@qti.qualcomm.com> <CAMm+LwjqNXrZCbXAgJjB0isTb5VCQVHmBR2X55JO6ZaBLuGZTA@mail.gmail.com> <9ECDC905D01276A63A779E35@caldav.corp.apple.com> <CAMm+Lwjgt3ptuC+LuaHoN00-USQBi4L3nL6kfY+ouStP8+t2TA@mail.gmail.com>
Organisation: g10 Code GmbH
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
OpenPGP: id=1E42B367; url=finger:wk@g10code.com
Date: Mon, 01 Sep 2014 12:11:15 +0200
In-Reply-To: <CAMm+Lwjgt3ptuC+LuaHoN00-USQBi4L3nL6kfY+ouStP8+t2TA@mail.gmail.com> (Phillip Hallam-Baker's message of "Thu, 28 Aug 2014 17:44:09 -0400")
Message-ID: <87d2bfps58.fsf@vigenere.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/n5EtDoHi7O5PCf0vB4q16G8aFLk
Cc: Cyrus Daboo <cyrus@daboo.name>, Pete Resnick <presnick@qti.qualcomm.com>, endymail <endymail@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Endymail] Off we go...
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 10:16:46 -0000

On Thu, 28 Aug 2014 23:44, phill@hallambaker.com said:

> * Easy way to migrate encryption keys into new devices.
>
> * Key recovery mechanisms so people don't loose their mail by accident.

These are closely related.  It is commonly known as backup/restore.
Fortunately we only need to care about the secret key which means we
need to backup 32 bytes plus an identification of 20 or 32 bytes for the
public key.  This can easily be achieved using a QR code.  Print it out
and for restore take a photo of it.  Right, this opens new paths for
local attacks on the secret key but if an attacker already has control
over the local device, we are anyway in game over state.  And it would
be a good start to make that easier.

The current protocols do not allow for an abbreviated backup scheme of
the secret key but it won't not be too complicated to do that.  As long
as we can assume that the public key is really public.  Data protection
rules may be a problem here.

> * Easy key rollover

In case of key compromise or for forward security?  The latter is more
problematic because you need to take the key offline but if you still
want to decrypt old messages (may be just 1 week, 1 month old) there
needs to be an easy way to restore them.

> be solved. But what has happened in the past is that they have been
> shuffled under the mat as 'advanced user problems'.

Yeah.


Salam-Shalom,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.