[Gpg4win-devel] Gpg4win without claws

[Werner Koch]

On Tue,  4 Aug 2015 16:05, ticho at claws-mail.org said:

> thanks for the first step. We were planning to make a new Claws Mail
> Windows release in coming days, so now we can as well drop GPG&deps in
> it, and add similar message about where to get Gpg4win package.

We may want to solve one problem here right away: gpgme looks for gpg2
by locating gpgconf in the installation directory of the gpgme DLL.

Now Claws will install its own gpgme DLL (the glib version) and thus
gpgme can't find gpgconf using the standard way and will use a fallback.

GPGME locates GnuPG by looking for gpgconf.exe here:

  1. Install directory of the used gpgme DLL or the application if
     statically linked.

  2. Using the registry key "HKLM\Software\GNU\GnuPG:Install Directory".

  3. Below CSIDL_PROGRAM_FILES in the directory "GNU\GnuPG".

If that all does not work gpgme will try to use gpg 1.4.

So this won't be a problem with current Gpg4win because that is indeed
installed at (3).  However if the registry key is set we will run into the
same problems we has before we tried the install directory first.

I would very much like to remove the registry key entirely to solve the
latter but that might also result in problems.

Now, the GnuPG 2.1 installer installs gnupg below CSIDL_PROGRAM_FILES in
the directory "GnuPG\bin".  What about adding another check between 1
and 2:

   1.5 Below CSIDL_PROGRAM_FILES in the directory "GnuPG\bin".

This way we would be prepared for GnuPG 2.1 while not risking major
incompatibilities and we could keep the registry key.

Shall I implement that for GPGME?


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.