Page MenuHome GnuPG
Create Task
Maniphest T3467

Wrong installation directory for GnuPG
Closed, InvalidPublic
Actions

Description

Hello all together,

I'm using a configuration file for the automatic installation as described in Annex C of the compendium and setting up the installation path as a parameter:

gpg4win /S /C=c:\tmp\gpg4win_setup.ini D=C:\Applications\gpg4win

All components are installed below the given directory, except GnuPG itself. Irrespective of the setting, the installation is carried out in the standard directory, parallel to gpg4win.
This also happens in the interactive installation.

The behavior differs from version 2.x, where GnuPG is installed below gpg4win, as desired by us.

Best regards,
Jens

Details

Version
3.0.0

Event Timeline

JUB created this task.Oct 26 2017, 3:15 PM
• werner closed this task as Invalid.Oct 26 2017, 4:41 PM
• werner added a subscriber: • werner.

Right, this differs. GnuPG is now installed at a well known location. Actually the Gpg4win installer includes the standard GnuPG installer and it is possible to update just GnuPG without a need to update the entire gpg4win.
This avoid multiple installs of GnuPG with all its problems.

JUB added a comment.Oct 26 2017, 4:51 PM

But how can I influence the target directory for GnuPG during an automatic installation? We are not using the default directories.

• werner added a comment.Oct 27 2017, 1:34 PM

You can't and you shall not.

JUB added a comment.Oct 27 2017, 3:08 PM

Why I shouldn't do that? Sorry, but I can't see a reason to pin the installation directory to a predefined value ("well known location").
Then, why can I still change the installation directory for gpg4win?

The standard GnuPG installer allows to define a target directory for a silent setup, for instance:

gnupg-w32-2.2.1-20170919-bin.exe /S /D=C:\Applications.32\GPG

We are already doing that on the automatic deployment of gnupg on our clients.
The fixation to the well known location is limiting the control over the software package.

In the gpg4win installer gnupg is still essential. The installer doesn't take care about the existence of a previously (maybe newer) standard GnuPG package.

Best regards,
Jens