Page MenuHome GnuPG
Create Task
Maniphest T7297

Kleopatra: Improve support for V5 fingerprints
Testing, NormalPublic
Actions

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.)

Revisions and Commits

rLIBKLEO Libkleo
rLIBKLEO669f35f0f1a3 Show key ID instead of short key ID in KeyRequester
rLIBKLEObee913b8d50d Fix pretty printing of signature created with V5 signing subkey
rLIBKLEOc68e2fa23829 Add findSigner and make findSigners work for signing subkeys
rLIBKLEO2eddfb73f3d2 Allow lookup of subkey by fingerprint
rLIBKLEO392c853cd8c6 Display correct key ID for V5 keys
rLIBKLEO861a091fbd37 Use same formatting for V5 fingerprints as gpg
rLIBKLEO9d7dfbc70704 Make check for fingerprints more strict
rKLEOPATRA Kleopatra
rKLEOPATRA57b08467f91b Fix "kleopatra --query" for V5 fingerprints
rKLEOPATRAcc391259611e Display correct key ID for V5 keys

Related Objects

Event Timeline

• ikloecker triaged this task as Normal priority.Sep 23 2024, 12:33 PM
• ikloecker created this task.
• ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ikloecker added a commit: rLIBKLEO9d7dfbc70704: Make check for fingerprints more strict.Sep 23 2024, 4:05 PM
• ikloecker added a commit: rLIBKLEO861a091fbd37: Use same formatting for V5 fingerprints as gpg.
• ikloecker added a commit: rLIBKLEO392c853cd8c6: Display correct key ID for V5 keys.
• ikloecker added a commit: rKLEOPATRAcc391259611e: Display correct key ID for V5 keys.Sep 23 2024, 4:22 PM
• ikloecker added a commit: rLIBKLEO2eddfb73f3d2: Allow lookup of subkey by fingerprint.Sep 23 2024, 5:14 PM
• ikloecker added a commit: rKLEOPATRA57b08467f91b: Fix "kleopatra --query" for V5 fingerprints.Sep 23 2024, 5:18 PM
• ikloecker added a commit: rLIBKLEOc68e2fa23829: Add findSigner and make findSigners work for signing subkeys.Sep 24 2024, 4:31 PM
• ikloecker added a commit: rLIBKLEObee913b8d50d: Fix pretty printing of signature created with V5 signing subkey.
• ikloecker mentioned this in T7301: Kleopatra: Remove any usage and mention of the short Key ID.Sep 25 2024, 11:48 AM
• ikloecker added a commit: rLIBKLEO669f35f0f1a3: Show key ID instead of short key ID in KeyRequester.Sep 26 2024, 3:06 PM
• 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.Mon, May 19, 11:47 AM
timegrid added a subscriber: timegrid.Tue, May 20, 4:30 PM

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.Tue, May 20, 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.)