Possible --list-keys bug in 1.2.3

[David Shaw]

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

On Wed, Aug 27, 2003 at 11:48:53PM +0200, Martin Ehmsen wrote:
> Hi...
> 
> I think I have found a bug in gnupg-1.2.3.
> It has to do with listing the keyring filename. It all started because 
> psi (a jabber client) couldn't parse the output from gnupg-1.2.3.
> Is the following the intended output from gnupg??:
> 
> #gpg --fixed-list-mode --with-colons --list-public-keys
> tru::0:1052827211:1122902031
> pub:u:1024:17:A028881BDEA361F6:1052827202:1122902031::u:::scESC:
> uid:u::::::::Martin Ehmsen <ehmsen at imada.sdu.dk>:
> ... and so on
> 
> #gpg --fixed-list-mode --list-public-keys
> /home/ehmsen/.gnupg/pubring.gpg
> -------------------------------
> pub 1024D/DEA361F6 2003-05-13 Martin Ehmsen <ehmsen at imada.sdu.dk>
> sub 2048g/0D121BB5 2003-05-13
> ... and so on
> 
> The problem is the missing:
> /home/ehmsen/.gnupg/pubring.gpg
> -------------------------------
> in the first output where --with-colons is turned on. Even with the 
> --show-keyring option on, it dosen't show the keyring filename when 
> --with-colons in turned on.
> Is this a bug or is this the intended behaviour??
> (This is has changed between 1.2.2 and 1.2.3.)

Believe it or not, this is a bug *fix* in 1.2.3.  The --with-colons
output wasn't supposed to contain the keyring filename.  The
- --with-colons output is for machine parsing, and the keyring filename
was for human parsing (note the underline).

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

iHEEARECADEFAj9RK1oqGGh0dHA6Ly93d3cuamFiYmVyd29ja3kuY29tL2Rhdmlk
L2tleXMuYXNjAAoJEOJmXIdJ4cvJO+IAoLHOP1k1pXQZFWmb19f8DYtFphxQAJwI
xdVw2Dt1dNLV0qy5Fr08yuHLXg==
=/YHi
-----END PGP SIGNATURE-----