Re: V5 key packet format requirements
Edwin Woudt <edwin@woudt.nl> Fri, 03 February 2006 13:22 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F50tZ-0006CB-My for openpgp-archive@megatron.ietf.org; Fri, 03 Feb 2006 08:22:38 -0500
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25994 for <openpgp-archive@lists.ietf.org>; Fri, 3 Feb 2006 08:20:59 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k13D57xi029925; Fri, 3 Feb 2006 05:05:07 -0800 (PST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id k13D57UE029924; Fri, 3 Feb 2006 05:05:07 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from smtpq2.groni1.gr.home.nl (smtpq2.groni1.gr.home.nl [213.51.130.201]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k13D56Up029918 for <ietf-openpgp@imc.org>; Fri, 3 Feb 2006 05:05:07 -0800 (PST) (envelope-from edwin@woudt.nl)
Received: from [213.51.130.188] (port=49940 helo=smtp3.groni1.gr.home.nl) by smtpq2.groni1.gr.home.nl with esmtp (Exim 4.30) id 1F50cb-000784-Fg; Fri, 03 Feb 2006 14:05:05 +0100
Received: from cc718542-b.ensch1.ov.home.nl ([82.75.228.134]:6969 helo=[10.42.42.23]) by smtp3.groni1.gr.home.nl with esmtp (Exim 4.30) id 1F50ca-0007Ui-9l; Fri, 03 Feb 2006 14:05:04 +0100
Date: Fri, 03 Feb 2006 14:05:34 +0100
From: Edwin Woudt <edwin@woudt.nl>
To: "Daniel A. Nagy" <nagydani@epointsystem.org>, OpenPGP <ietf-openpgp@imc.org>
Subject: Re: V5 key packet format requirements
Message-ID: <FA596539681BD627562D1FC4@[10.42.42.23]>
In-Reply-To: <20060202160713.GB18144@epointsystem.org>
References: <20060202160713.GB18144@epointsystem.org>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-AtHome-MailScanner-Information: Neem contact op met support@home.nl voor meer informatie
X-AtHome-MailScanner: Found to be clean
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>
Content-Transfer-Encoding: 7bit
--On 2-2-2006 17:07 +0100 "Daniel A. Nagy" <nagydani@epointsystem.org> wrote: > > 1. Exclude creation date from fingerprint and key ID hash computation (and > maybe from the key packet, too -- it belongs to the self-signature). This > would mean that the key fingerprint and ID depend only on the actual key > (key material + algorithm). IMHO, things that have nothing to do with the user ID should not be in a self-signature, but in a direct key signature (type 0x1F) instead. > 2. Scrap encrypted private keys. We already have a symmetrically encrypted > container format with sufficient integrity protection, so there is no > reason to maintain another one. Just put the unencrypted private key > packet into that container, if you need encryption. This will reduce the > number of things to worry about and make the security of OpenPGP easier > to assess and maintain. Agreed. > 4. Support for exporting and importing subkeys. Why is this needed? Isn't this possible already using the current (V4) packet formats? -- Edwin
- V5 key packet format requirements Daniel A. Nagy
- Re: V5 key packet format requirements Ben Laurie
- Re: V5 key packet format requirements Ben Laurie
- Re: V5 key packet format requirements Edwin Woudt
- Re: V5 key packet format requirements Daniel A. Nagy
- Re: V5 key packet format requirements Edwin Woudt
- Re: V5 key packet format requirements Ian G
- Re: V5 key packet format requirements Daniel A. Nagy
- Re: V5 key packet format requirements Adam Back
- Re: V5 key packet format requirements Konrad Rosenbaum
- Re: V5 key packet format requirements Daniel A. Nagy
- Re: V5 key packet format requirements Jon Callas