-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
John Clizbe wrote:
FWIW, the look for gpg.conf
in same directory as executable idea, falls apart if you ever need to have
additional copies of GnuPG in the case of different OS or CPUs.
There's not really a directory that W32, Mac, and*nix
Andrew Berg wrote:
In instances where GPG is used on a portable drive and used on
different machines, it is much better to have gpg.conf read from the
same directory as GPG rather than read from %appdata%\gnupg or
~/.gnupg. Just to have it check the same directory, then
%appdata%\gnupg or
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Peter S. May wrote:
Andrew Berg wrote:
In instances where GPG is used on a portable drive and used on
different machines, it is much better to have gpg.conf read from the
same directory as GPG rather than read from %appdata%\gnupg or
Andrew Berg wrote:
Peter S. May wrote:
Andrew Berg wrote:
In instances where GPG is used on a portable drive and used on
different machines, it is much better to have gpg.conf read from the
same directory as GPG rather than read from %appdata%\gnupg or
~/.gnupg. Just to have it check the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
In instances where GPG is used on a portable drive and used on
different machines, it is much better to have gpg.conf read from the
same directory as GPG rather than read from %appdata%\gnupg or
~/.gnupg. Just to have it check the same
