in https://lists.gnupg.org/pipermail/gnupg-devel/2016-January/030748.html,
Werner suggests:
Let me do this along with --with-fingerprint being the default and a new
option --without-fingerprint.
I'm opening this ticket to track the suggestion.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T1445: keyid-format fingerprint
- Mentioned Here
- rG7257ea2d4502: gpg: Use --keyid-format=none by default.
Event Timeline
Comment Actions
The current --with-fingerprint output is
pub dsa2048/F2AD85AC1E42B367 2007-12-31 [SC] [expires: 2018-12-31]
Key fingerprint = 8061 5870 F5BA D690 3336 86D0 F2AD 85AC 1E42 B367
uid [ full ] Werner Koch <wk@gnupg.org>
One problem I have with this format is the c+p of the fingerrpint is
not easy, because you need to mark the entire fingerprint and then use
quotes to use it. What about changing the default format (i.e. w/o
any fingerprint options to
pub dsa2048/F2AD85AC1E42B367 2007-12-31 [SC] [expires: 2018-12-31]
80615870F5BAD690333686D0F2AD85AC1E42B367
uid [ full ] Werner Koch <wk@gnupg.org>
or
pub dsa2048/1E42B367 2007-12-31 [SC] [expires: 2018-12-31]
80615870F5BAD690333686D0F2AD85AC1E42B367
uid [ full ] Werner Koch <wk@gnupg.org>
or
pub dsa2048 2007-12-31 [SC] [expires: 2018-12-31]
80615870F5BAD690333686D0F2AD85AC1E42B367
uid [ full ] Werner Koch <wk@gnupg.org>
or aligned in some other way?
Personally I would like to keep the long keyid at least for subkeys
because it makes the key listing easier to read and forced selection
of a signing subkey easier. However, removing information which is
in most cases useless and partly dangerous has a higher priority.
Thus a listing of my key may look like this:
pub dsa2048 2007-12-31 [SC] [expires: 2018-12-31]
80615870F5BAD690333686D0F2AD85AC1E42B367
uid [ full ] Werner Koch <wk@gnupg.org>
uid [ full ] Werner Koch <wk@[...]>
uid [ full ] Werner Koch <werner@[...]>
sub dsa1024 2011-11-02 [S]
sub rsa2048 2014-01-02 [E] [expires: 2016-12-31]
To implement that I would indeed suggest a keyid format "none" which
will be the default and select the above new listing format.
Comment Actions
This looks great to me. I've always been frustrated by the c+p difficulty.
Does it make sense to put an "fpr" at the beginning of the fingerprint line, to
match with "pub" and "uid" ?
For example:
pub dsa2048 2007-12-31 [SC] [expires: 2018-12-31]
fpr 80615870F5BAD690333686D0F2AD85AC1E42B367
uid [ full ] Werner Koch <wk@gnupg.org>
Have you started work on this change or would you like patches?
Comment Actions
I tried it but I think it looks prettier without. A rationale might be that the
fingerprint is a property of the "pub" (public key) and the line should be
considered a continuation line.
Comment Actions
This is the current output with keyid-format=none
pub dsa2048 2007-12-31 [SC] [expires: 2018-12-31]
80615870F5BAD690333686D0F2AD85AC1E42B367
uid [ full ] Werner Koch <wk@gnupg.org>
uid [ full ] Werner Koch <wk@[...]>
uid [ unknown] Werner Koch <werner@[...]>
sub dsa1024 2011-11-02 [S]
sub rsa2048 2014-01-02 [E] [expires: 2016-12-31]
The problem I have is how to decide when to use the compact fingerprint format.
My idea is to always use the compact format unless --fingerprint switched back
to the old format (which is easier to read).
Comment Actions
Just pushed the --keyid-format=none feature. Changing the default will be done
with another commit.
Comment Actions
7257ea2 switches to none.
There is also a new option --with-subkey-fingerprint which keeps the compact
fingerprint format also for subkeys. The Lead-in text for fingerprints n the
listing is in any case not anymore printed if keyid-format is none.