Problems with listing secret keys in GnuPG 1.2.1

[David Shaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Jun 13, 2003 at 03:14:24AM -0500, Robert J. Hansen wrote:
> > Do you have those backwards?  The listing when you give the username
> > should be the first example, not the second.
> 
> Not as far as I know.  Unfortunately, the box I did the manual copy from is
> unavailable.  Another box, with almost exactly the same private keyring
> (it's missing a UID I added to the other one), gives the following.
> (Unfortunately, my $%&(! Win32 ssh client doesn't support cut-and-paste, so
> once more this is all manual entry--apologies if I miss a colon or
> something.)

Okay, just making sure.  The example you give in this email confirms
what I see as well.

This is resolved in 1.2.3 by not giving validity information in the
with-colons secret key listing.  The proper resolution (to give the
validity information of the corresponding public key) will be in 2.0.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-cvs (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc

iD8DBQE+7OHw4mZch0nhy8kRAp5nAKC837uWCVVgRiBSoPgVWIJk4USZ3QCff14H
lMXFPb2byU5WUa/qFJCKVIo=
=Y7Wh
-----END PGP SIGNATURE-----