Bug#579863: GnuPG::Interface should always use --fixed-list-mode [PATCH]

Daniel Kahn Gillmor dkg at fifthhorseman.net
Sat May 1 18:57:17 UTC 2010

Package: libgnupg-interface-perl

the --fixed-list-mode option for gpg is designed for cleaner/simpler
machine-parseable output:


> Do not merge primary user ID and primary key in --with-colon listing
> mode and print all timestamps as seconds since 1970-01-01. 

As of version 2.0.10 (Jan 2009), gpg2 uses --fixed-list-mode by default:


As a consequence, using gpg2 with GnuPG::Interface produces an extra
GnuPG::UserID object on each key with an empty string and no signatures.
 Worse, this empty User ID inherits the validity of the key itself,
which is the highest validity of any other User ID.

As a result, every key that has a fully-valid User ID appears to also
have a full-valid User ID (albeit one with no signatures) of "".

The attached patch enforces the use of --fixed-list-mode (so both gpg 1
and gpg 2 will behave in the same way) and cleans up the creation of the
mistaken initial empty User ID.

Thanks for GnuPG::Interface!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: use_fixed_list_mode.patch
Type: text/x-patch
Size: 713 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20100501/4348bdf7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 892 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20100501/4348bdf7/attachment.pgp>

More information about the pkg-perl-maintainers mailing list