Page MenuHome GnuPG

Kleopatra: Improve support for V5 fingerprints
Testing, NormalPublic

Description

Support for V5 fingerprints (32 bytes) in Kleopatra shall be improved. In particular:

  1. Display format: Show the first 25 bytes in 10 blocks of 5 hex characters separated by a space character (i.e. the same format as used by gpg -k --with-fingerprint).
  2. Ensure that we use the first 8 bytes if we show the key ID. (For V4 fingerprints the key ID is the last 8 bytes.)

Event Timeline

ikloecker created this task.
ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
ikloecker changed the task status from Open to Testing.Sep 26 2024, 4:42 PM

V5 keys should now work as good as V4 keys in Kleopatra. For testing create a "Curve 448" key and then try a few things. Everything should just work because it works for gpg. Kleopatra doesn't really do anything special for V5 keys.

I have mostly looked for possible assumptions about the length of a V4 fingerprint (40 hex chars) and stumbled over code deriving the (short or normal) key ID from the fingerprint using the last few characters which is wrong for V5 keys where the key ID is the first few characters of the fingerprint.

ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.May 19 2025, 11:47 AM

tested on gpg4win-4.4.1-beta59@win10

  • the keyid (first 8 bytes) seem ok:

  • but the ticket description above states, that the format should be 10 * 5 = 50 hex chars (first 25 byte), not 16 * 4 = 64 (all 32 byte)?


ikloecker edited projects, added gpd5x; removed Restricted Project.May 20 2025, 9:20 PM

The changes have only been implemented for the upcoming Qt 6 based Kleopatra, i.e. Gpg4win 5. I have updated the project tags accordingly.

In general, any ticket that is tagged with gpgcom, but not with vsd, has not been backported for VSD 3.x or Gpg4win 4.x. (The exception might be tickets that have been set to Testing before we switched development to Gpg4win 5 by default in May 2024.)

Tested on gpg4win-5.0.0-beta336 @ win10.

Issues found:

  • tooltip "fingerprint" in cert select on sign/encrypt or notepad or certification
  • fingerprint in smarcard key slot overwrite dialog (not formatted in general)
  • fingerprint in certification revocation confirmation (not formatted in general)

Everything else looks good to me:




I guess that the missing formatting of fingerprint or key ID isn't restricted to v5 keys. -> separate ticket

General issues with unformatted fingerprints/keyids moved into T7707.