Re: Fixing the secret keys, and a small apology
Jon Callas <jon@callas.org> Thu, 06 September 2001 19:15 UTC
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06440 for <openpgp-archive@odin.ietf.org>; Thu, 6 Sep 2001 15:15:52 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id f86J5wr12067 for ietf-openpgp-bks; Thu, 6 Sep 2001 12:05:58 -0700 (PDT)
Received: from merrymeet.com (merrymeet.com [63.73.97.162]) by above.proper.com (8.11.6/8.11.3) with ESMTP id f86J5uD12062 for <ietf-openpgp@imc.org>; Thu, 6 Sep 2001 12:05:57 -0700 (PDT)
Received: from [192.168.1.180] (64.69.113.115) by merrymeet.com with ESMTP (Eudora Internet Mail Server 3.0.3); Thu, 6 Sep 2001 12:05:47 -0700
Mime-Version: 1.0
X-Sender: jon@merrymeet.com
Message-Id: <p05100320b7bd6810c94d@[192.168.1.180]>
In-Reply-To: <87y9nuw09p.fsf@alberti.gnupg.de>
References: <p05100309b7baf2e20a43@[192.168.1.180]> <87y9nuw09p.fsf@alberti.gnupg.de>
Date: Thu, 06 Sep 2001 12:02:47 -0700
To: Werner Koch <wk@gnupg.org>
From: Jon Callas <jon@callas.org>
Subject: Re: Fixing the secret keys, and a small apology
Cc: ietf-openpgp@imc.org
Content-Type: text/plain; charset="us-ascii"
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>
At 9:43 AM +0200 9/5/01, Werner Koch wrote: >This is fine with me. > >Another question is the format. Should we include only the public >parameters or more stuff in the MDC? A solution I would like to see >is to just hash the fingerprint of the key along with the secret >parameters. I predict that in future, implementations will use the >fingerprint to identify a key (and not just the keyID) and therefore >it is steadily available. As a couple people noted, I was probably too glib. The byte isn't actually part of the S2K, it's a marker that says that an S2K follows. I think that 254 would denote that we have an S2K and a hash. Let's not call it an MDC, because we're going to get confused if we do. The questions I see are: Hash of what? Is it inside or outside the envelope? Where is it placed? Are there any developers that want to come up with a design? Jon
- Fixing the secret keys, and a small apology Jon Callas
- Re: Fixing the secret keys, and a small apology Michael Young
- Identifying revoked certificates Michael Young
- Re: Fixing the secret keys, and a small apology Florian Weimer
- Re: Fixing the secret keys, and a small apology Werner Koch
- Re: Fixing the secret keys, and a small apology Michael Young
- Re: Fixing the secret keys, and a small apology Michael Young
- Re: Fixing the secret keys, and a small apology Werner Koch
- Re: Fixing the secret keys, and a small apology Jon Callas
- Re: Identifying revoked certificates Jon Callas
- Re: Identifying revoked certificates David Shaw
- Re: Identifying revoked certificates Michael Young
- Re: Identifying revoked certificates Jon Callas
- Re: Identifying revoked certificates Jon Callas
- Re: Identifying revoked certificates Michael Young
- Re: Identifying revoked certificates Werner Koch
- Re: Identifying revoked certificates Michael Young
- Re: Identifying revoked certificates Werner Koch