Page MenuHome GnuPG

gpg --quiet --quick-sign-key is not quiet
Open, LowPublic

Description

When i run gpg --quiet --quick-sign-key, it emits the following to stdout:

sec  rsa3072/3E0FD8A37C52EA70
     created: 2019-07-01  expires: 2021-06-30  usage: SC  
     trust: ultimate      validity: ultimate
 Primary key fingerprint: 8D03 385D 14B9 CA0F B627  A47C 3E0F D8A3 7C52 EA70

     test key

This key is due to expire on 2021-06-30.

If i use --with-colons, it is even worse: a mix of colon-delimited and non-colon-delimited output:

sec:u:3072:1:02F36CACB7CBA05D:1562010107:1625082107::u:::sc
fpr:::::::::40CE4A61FC5064BDCC7E051802F36CACB7CBA05D:
ssb:u:3072:1:83FD067A1CCFE8F7:1562010107:0:::::e
fpr:::::::::F83019A571947A7397331CB683FD067A1CCFE8F7:
uid:u::::::::test key:::S9 S8 S7 S2 H10 H9 H8 H11 H2 Z2 Z3 Z1,mdc,no-ks-modify:1,pm::

This key is due to expire on 2021-06-30.

Note that there is also an additional line of whitespace at the top and bottom too.

Details

Version
2.2.16

Event Timeline

dkg updated the task description. (Show Details)
werner triaged this task as Normal priority.Jul 1 2019, 9:58 PM

Quiet tricky to get right; needs some rework.

does the removal of the gpg22 tag mean that it will not be possible to rely on colon-delimited output for the gpg 2.2 series?

werner lowered the priority of this task from Normal to Low.Feb 10 2021, 3:05 PM