Page MenuHome GnuPG

Kleopatra: Always use gpgme to find the GnuPG binaries
Testing, NormalPublic

Description

Some code paths of Kleopatra don't use gpgme to find the GnuPG installation. Instead they look into the registry. Usually, this works because there's only one installation of GnuPG, but with T7528: Make it possible to run Kleopatra VSD and Kleopatra GPD in parallel this will change. Therefore, Kleopatra should always use gpgme to find the GnuPG installation.

Event Timeline

ikloecker created this task.
ikloecker moved this task from Backlog to WIP on the gpd5x board.

I think we also want this for VSD 3.4.

Fixed and backported for VSD 3.4.

Notes for testing: The following things are affected, but if anything then the new implementation should fix problems that occurred because a wrong GnuPG installation was used:

  • VSD/GPD: Checking the signature of the VERSION file (path of gpgv.exe, path of GnuPG's signing keys)
  • Gpg4win/?: Update check (path of gpg-connect-agent.exe)
  • all: Handling of archives, i.e. encrypt, decrypt, etc. (path of gpgtar)
  • all: Listing of versions of backend components in About dialog (path of gpgconf)
  • all: Start and restart of gpg-agent (path of gpgconf to launch/kill gpg-agent)
  • all: Change root certificate trust (path of gpgconf to reload gpg-agent)
  • all: Certificate Dump in Certificate Details of S/MIME certificates (path of gpgsm)
  • all: Clear CLR Cache (path of gpgsm)
  • all: Dump CRL Cache (path of gpgsm)
  • all: Import CRL From File (path of gpgsm)
  • all: Publish on Server (path of gpg)
  • all: Generate revocation certificate in Certificate Details of (own) OpenPGP certificates (path of gpg)
ikloecker changed the task status from Open to Testing.Thu, Dec 11, 3:05 PM
ikloecker moved this task from Backlog to WIP on the vsd34 board.
ikloecker mentioned this in Unknown Object (Maniphest Task).Mon, Dec 15, 10:00 AM