>
> 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 o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Saturday 17 December 2016 at 1:16:13 AM, in
, 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 issu
Is there somewhere I can check what settings were added and removed in
the "update"?
--
Alexandre Oliveira
167F D82F 514A E8D1 2E9E
C62D 1B63 9D4A 7E9D DA9D
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/
> 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
Hello.
I'm a newbie when it comes to using GnuPG and PGP. I have 2 different
versions currently installed in my system, so 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.
Thank you.
_
