Common directory for different installs of GnuPG

[MFPA]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



On Saturday 17 December 2016 at 1:16:13 AM, in
<mid:2ca1ee78-649d-d358-ebfa-fd2fd165d94e at sixdemonbag.org>, Robert J.
Hansen wrote:-


>> I'd like to know if setting both versions to point
>> at the same
>> directory to obtain the pubring.gpg, secring.gpg
>> and trustdb.gpg
>> files can cause critical issues.

> Unlikely.  It's technically possible to have
> configuration files that
> don't work with 1.4 and 2.0/2.1, but it involves
> options you likely
> shouldn't have set in the first place.


You can use different configuration files. A couple of years ago, dkg
shared [0]:-

> gpg 2.1.0 will look for the following files in $GNUPGHOME and choose the
> first one it finds:
>
>  gpg.conf-2.1.0
>  gpg.conf-2.1
>  gpg.conf-2
>  gpg.conf
>
> gpg 1.4.18 will do the same sort of search:
>
>  gpg.conf-1.4.18
>  gpg.conf-1.4
>  gpg.conf-1
>  gpg.conf

[0] <https://www.mail-archive.com/gnupg-users@gnupg.org/msg26542.html>


- --
Best regards

MFPA                  <mailto:2014-667rhzu3dc-lists-groups at riseup.net>

The secret to creativity is knowing how to hide your sources.
-----BEGIN PGP SIGNATURE-----

iL4EARYKAGYFAlhVWh9fFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl
bnBncC5maWZ0aGhvcnNlbWFuLm5ldDMzQUNFRDRFRTkxMzRFRUJERTZBODUwNjE3
MTJCQzQ2MUFGNzc4RTQACgkQFxK8Rhr3eOQDqgD/bq5bp2+Gt2w3CWQ0SROMvLBu
ffCrw7IlhPAfvRJoZnYA/Rm8WvN8etm3a5lDFXvcI7GMr1t50fyDtR5n0dPN02UO
iQF8BAEBCgBmBQJYVVouXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXw+wcH/R7DhPSl3v0ScIbLTdDxt5SZ
WsFnAxNp9ur2qzsfHhVFp6utLi3QLRI5lievbs4GSaLGgpTKC/BtbiIo+GKY0XxS
/mlma3GLHVIYvMiSp64I72O+jKU7fXaqwmmkKK9cEvjdCnevPQZrORuDHeeX1+WH
9ZzQU11iIPww28zvgQH5U30FDKYuN3BWw49ZIZlPM354iBxIg3x3s01EB9PUgdNn
rtUlGBTvBvZBZou8nRHNwbkBpYjMkTzGarqztj78YL0JQnUcIHYSf7F+jycqO8ib
cRR/5tdWsPIBRHkuUhOUZ2WaSb9YmQGPngGn22KFwubJ3ZOnv2nNXvtcBcajx6M=
=T3iL
-----END PGP SIGNATURE-----