diff options
| author | Andre Heinecke <[email protected]> | 2018-05-17 15:41:53 +0000 |
|---|---|---|
| committer | Andre Heinecke <[email protected]> | 2018-05-17 15:46:12 +0000 |
| commit | e04b8142df21a49e6c4a3f8234cc14bfec217222 (patch) | |
| tree | 4c4b064b58a76e604834e1d1796f18821254635e /lang/python/examples/howto/decrypt-file.py | |
| parent | core: Always fail if an OpenPG message is not integrity protected. (diff) | |
| download | gpgme-e04b8142df21a49e6c4a3f8234cc14bfec217222.tar.gz gpgme-e04b8142df21a49e6c4a3f8234cc14bfec217222.zip | |
core, w32: Add w64 handling for regkeys
* src/w32-util.c (_gpgme_get_gpg_path): Use new defines.
(GNUPG_REGKEY_2): x64 aware regkey as used by GnuPG in Gpg4win 2.x
(GNUPG_REGKEY_3): x64 aware regkey as used by GnuPG in Gpg4win 3.x
(_gpgme_get_gpgconf_path): Use new regkeys. Add another fallback.
--
This should fix more "unsupported protocol" issues if Gpg4win /
GnuPG is installed in a non standard path on 64bit systems.
The regkey handling is similar to that of gpgex and gpgol.
GnuPG-Bug-Id: T3988
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions