Page MenuHome GnuPG
Create Task
Maniphest T7758

Kleopatra: Make the registry path for the GnuPG install directory customizable
Testing, NormalPublic
Actions

Description

Currently, the registry path and registry key is hard-coded to Software\\GnuPG with key Install Directory in libkleo. For VSD/GPD this needs to be customizable.

for 64 bit VSD: Software\\GnuPG:VSD Install Directory
for 64 bit: Software\\GnuPG:Install Directory
for other (i.e. 32bit): Software\\Gpg4win:Install Directory

Revisions and Commits

rLIBKLEO Libkleo
rLIBKLEO9ccc6e3a2cc2 Allow build-time customization of registry key to find GnuPG
rW Gpg4win
rWfb1f9cc1100f Configure libkleo with different GnuPG install dir registry key for VSD

Related Objects
Search...

Event Timeline

• ikloecker triaged this task as Normal priority.Jul 30 2025, 4:15 PM
• ikloecker created this task.
• ikloecker added a parent task: T7528: Make it possible to run Kleopatra VSD and Kleopatra GPD in parallel.
• ikloecker updated the task description. (Show Details)Jul 30 2025, 4:18 PM
• ikloecker moved this task from Backlog to WIP on the gpd5x board.Jul 31 2025, 9:12 AM
• werner updated the task description. (Show Details)Jul 31 2025, 9:39 AM
• werner added a project: Windows.
• ikloecker added a commit: rLIBKLEO9ccc6e3a2cc2: Allow build-time customization of registry key to find GnuPG.Jul 31 2025, 4:13 PM
• ikloecker added a commit: rWfb1f9cc1100f: Configure libkleo with different GnuPG install dir registry key for VSD.
• ikloecker changed the task status from Open to Testing.Jul 31 2025, 4:21 PM

Kleopatra from VSD installations should now use gpgv from the GnuPG installed by VSD when verifying the signature of the VERSION file. GPD and Gpg4win installations both use gpgv from the GnuPG installed at the value of the registry key "Software\\GnuPG:Install Directory".

• werner awarded a token.Jul 31 2025, 8:39 PM
• ikloecker mentioned this in Unknown Object (Maniphest Task).Aug 4 2025, 9:37 AM
timegrid added a subscriber: timegrid.Sep 9 2025, 12:54 PM

This probably can only be tested with signed releases?

timegrid added a comment.Sep 9 2025, 1:07 PM

Note: If i set an invalid path in "Software\\GnuPG:Install Directory"

  • the gpgconf -X output does not change
  • the self-test Config File 'libkleopatrarc' fails with Error in archive definition tar: 'pack-command-openpgp' empty or not found
timegrid moved this task from WIP to QA on the gpd5x board.Sep 9 2025, 3:53 PM
• ikloecker added a comment.Mon, Sep 15, 12:06 PM
In T7758#205217, @timegrid wrote:

This probably can only be tested with signed releases?

Yes, this is customizable during the build. The registry path is burned into the executable. You need a VSD build to check that VSD uses a different registry path.

• ikloecker added a comment.Mon, Sep 15, 12:12 PM
In T7758#205218, @timegrid wrote:

Note: If i set an invalid path in "Software\\GnuPG:Install Directory"

  • the gpgconf -X output does not change
  • the self-test Config File 'libkleopatrarc' fails with Error in archive definition tar: 'pack-command-openpgp' empty or not found

I'd say that's expected behavior. "Software\\GnuPG:Install Directory" allows Kleopatra to find executables that come with GnuPG (which is installed by but separately from Gpg4win in a different location). gpgconf (and other components of GnuPG) simply look next to their own location and don't need to consult a registry path.