Page MenuHome GnuPG

GNUPG does not emit key-capabilities or expiration dates when --list-secret-keys is used without arguments
Closed, ResolvedPublic

Description

Compare the output of:

gpg --with-colons --list-secret-keys

gpg --with-colons --list-secret-keys .

The first form (without a matching argument) fails to print the key capabilities
in field 12. The second form (matching any user ID that contains a dot) prints
the key capabilities in field 12.

I believe that the first form *should* print the key capabilities, to bring it
in line with the behavior shown by the more commonly-used --list-keys.

Details

Version
1.4.9, 2.0.9

Event Timeline

dkg set Version to 1.4.9, 2.0.9.
dkg added a subscriber: dkg.

I've tested this with gnupg and gnupg2, and both seem to behave this way.

That is know. The capabilities are only listed with the public key.

We can't do anything about it without changing a lot of code.

Actually, the capabilities *are* listed with the secret keys, as long as you
provide a string to match against. The only case where they aren't listed is
when there's no matching string.

werner set Due Date to Jan 30 2009, 1:00 AM.Dec 5 2008, 6:22 PM

I see the problem but it is sill a lot of work to fix that.

A colleague just observed that expiration dates are also missing when
--list-secret-keys is used without a matching string.

dkg renamed this task from GNUPG does not emit key-capabilities when --list-secret-keys is used without arguments to GNUPG does not emit key-capabilities or expiration dates when --list-secret-keys is used without arguments.Oct 15 2010, 5:18 PM

There are 2.1 beta versions which support this.

werner claimed this task.
werner removed a project: Stalled.