gnupg 1.4 fixed-list-mode fails to take effect when listing keys
Closed, WontfixPublic

Description

running:

    gpg --fixed-list-mode --with-fingerprint --with-colons FILENAME

against a file that has OpenPGP keys in it produces colon-delimited output.
However, it uses the non-fixed-list-mode, even when --fixed-list-mode is present.

In 2.1.x, it provides fixed-list-mode output. This is a bug in
--fixed-list-mode in 1.4.x.

See also:

https://lists.gnupg.org/pipermail/gnupg-devel/2016-October/031724.html
https://lists.gnupg.org/pipermail/gnupg-devel/2016-October/031726.html

Details

Version
1.4
dkg set Version to 1.4.
dkg added a subscriber: dkg.
werner added a subscriber: werner.Oct 5 2016, 6:00 PM

I hesitate to fix this for 1.4 - if people are using this they are probably
working around it and a fix would break that.

werner lowered the priority of this task from Normal to Low.Oct 5 2016, 6:00 PM
dkg added a comment.Oct 5 2016, 6:49 PM

Agreed, but i ran into this while looking at python-gnupg, which is now failing
when using GnuPG 2.1. so they're facing breakage either way. It would be
better to have all current releases doing the expected behavior than to imagine
that we can bump this variance in behavior along indefinitely.

A major problem with gpg FILE-WITH-KEYS is that its behaviour was never well
defined and it is more a side effect than a a reguarl feature.

It should be fixed, however.

werner closed this task as Wontfix.Oct 20 2017, 12:54 PM
werner claimed this task.

In 2.2 we implemented --import-option show-only which dies the right thing, that is to use the reguarl key-listing code. Backporting this to 1.4 does not make sense - people should move on and use gpg 2.2.

So: Won't be fixed for 1.4.