Re: Fixing the secret keys, and a small apology
"Michael Young" <mwy-opgp97@the-youngs.org> Wed, 05 September 2001 01:40 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 VAA02880 for <openpgp-archive@odin.ietf.org>; Tue, 4 Sep 2001 21:40:01 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id f851NMC22274 for ietf-openpgp-bks; Tue, 4 Sep 2001 18:23:22 -0700 (PDT)
Received: from smtprelay1.adelphia.net (smtprelay1.adelphia.net [64.8.25.6]) by above.proper.com (8.11.6/8.11.3) with ESMTP id f851NAD22265 for <ietf-openpgp@imc.org>; Tue, 4 Sep 2001 18:23:20 -0700 (PDT)
Received: from mwyoung ([24.48.51.230]) by smtprelay1.adelphia.net (Netscape Messaging Server 4.15) with SMTP id GJ612B00.VDK for <ietf-openpgp@imc.org>; Tue, 4 Sep 2001 21:20:35 -0400
Message-ID: <003601c135a9$006a5bc0$fac32609@transarc.ibm.com>
From: Michael Young <mwy-opgp97@the-youngs.org>
To: ietf-openpgp@imc.org
References: <p05100309b7baf2e20a43@[192.168.1.180]>
Subject: Re: Fixing the secret keys, and a small apology
Date: Tue, 04 Sep 2001 21:20:39 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
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
-----BEGIN PGP SIGNED MESSAGE----- From: "Jon Callas" <jon@callas.org> > * Change the String-to-Key specifier. The solution here is adding in the > tag 254 to 3.7.2.1 and have 254 denote an improved S2K. I concur with Jon's analysis and conclusion (favoring a new pre-S2K tag). [It really has nothing to do with the S2K, though... it's the "pre-S2K" byte, and it simply says that the encrypted data (that *follows* the S2K) includes an MDC. But I'll accept it whatever wording is used. :-] -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.3 iQEVAwUBO5V9xWNDnIII+QUHAQFeGwgAiDTe0w/rBcoO+5MwKKOq125JW8StofkS J1kUgtTMgPBUAigSpNt1WLsajZk7IuYk+tS470k1PAx/3qj396nKeQ18TqdWNBUA lh1gSNlGeu3q2omFadC+TZTwNpuQpFvyGg9Te/qgYauENSnEaxCaMmRD3ShBEVyJ VPcGVi3qf3Q5E3C4qWnSbk48NBvQ+XbfmvGTQEVE5Ltwj/R/tY7FJReyeRbvzID6 2uHdVN7LzguqPAdPbAS7+jHX+dkWNvzkk9YN2nqQemwjpJz3pZJj/O8bj+Wb9Wy4 D8iYeSlTgHyj7qcHXhgS3SlscIuVLYrHWeuSvhgCL5wk7WRL7sqihw== =eG8B -----END PGP SIGNATURE-----
- 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