Re: [openpgp] saltpack on OpenPGP message format problems

Rick van Rein <rick@openfortress.nl> Wed, 02 March 2016 07:29 UTC

Return-Path: <rick@openfortress.nl>
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 CD6731A6FD8 for <openpgp@ietfa.amsl.com>; Tue, 1 Mar 2016 23:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 MZ8ql8TgDqBC for <openpgp@ietfa.amsl.com>; Tue, 1 Mar 2016 23:29:48 -0800 (PST)
Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5327B1A6FD6 for <openpgp@ietf.org>; Tue, 1 Mar 2016 23:29:48 -0800 (PST)
Received: from airhead.local ([83.161.146.46]) by smtp-cloud6.xs4all.net with ESMTP id QvVh1s00k10HQrX01vVibN; Wed, 02 Mar 2016 08:29:46 +0100
Message-ID: <56D69664.4040802@openfortress.nl>
Date: Wed, 02 Mar 2016 08:29:40 +0100
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <56BB0308.8020504@iang.org> <20160210160641.GA3090@singpolyma-liberty> <9A043F3CF02CD34C8E74AC1594475C73F4BED18C@uxcn10-5.UoA.auckland.ac.nz> <87lh6rbp5n.fsf@vigenere.g10code.de> <9A043F3CF02CD34C8E74AC1594475C73F4BEE527@uxcn10-5.UoA.auckland.ac.nz> <87d1s27wwa.fsf@vigenere.g10code.de> <CAMm+LwgyXQeymwkip-piHftA95K1RyzYYCUYt_X43zf_CLU5bA@mail.gmail.com>
In-Reply-To: <CAMm+LwgyXQeymwkip-piHftA95K1RyzYYCUYt_X43zf_CLU5bA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/DDYkXEgepuXrh-XojJUK_frpHdE>
Cc: Stephen Paul Weber <singpolyma@singpolyma.net>, "openpgp@ietf.org" <openpgp@ietf.org>, ianG <iang@iang.org>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
Subject: Re: [openpgp] saltpack on OpenPGP message format problems
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: Wed, 02 Mar 2016 07:29:51 -0000

Hello,

Phillip wrote:

> I think one point that has been massively overlooked by traditional
> crypto applications is the need to store private keys securely. In
> particular, it should be possible to fix private keys to a device such
> that the key can be used on that device but it is not possible to
> remove the key from the device and install it on another device
> without 'heroic' efforts (e.g. uncapping the CPU and reading it with a
> scanning electron microscope).

You seem to be talking of PKCS #11.  It's possible to use that under
OpenPGP but I've found the GnuPG implementation made it difficult.
Unlike the PGP card, which is more specific to the OpenPGP purpose,
this is a general standard for which many implementations exist in
USB sticks, ranging up to HSMs and even software low-end solutions.

FWIW, I had no problem implementing PKCS #11 for OpenPGP,

https://github.com/arpa2/tlspool/blob/master/tool/pgp11_genkey.c

This is only key generation (including self-signing) which is what I
needed for this project (which moves TLS to a daemon that uses PKCS #11)
but other things can also easily be moved to OpenPGP implementations.

Cheers,
 -Rick