-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi John,
> current directory issue, I am curious about why including it would result
> in a less secure situation.
I did not exactly say that it does. I said that I prefer it that way since it
uses well-defined places that I may look after. Add
Hello, Olav.
I sincerely appreciate your replies. Like the other poster asking about the
current directory issue, I too am curious about why including it would
result in a less secure situation. Perhaps an example of how so would be
helpful in this regard, at least for me or someone else who i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/31/2013 10:43 PM, Olav Seyfarth wrote:
| Hello, John.
|
|> Is that about right, then?
|
| Yes.
|
|> Would it not be true that gpg.exe would finally look in its own current
|> directory, which should suffice consequently for this purpose?
You
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hello, John.
> Is that about right, then?
Yes.
> Would it not be true that gpg.exe would finally look in its own current
> directory, which should suffice consequently for this purpose?
That's an authors' decision. I'm fine with it. It gives
Hi John,
some of your questions might be answered by reading README.W32 which you
can
find in the doc folder of GnuPG source tarballs:
| GnuPG makes use of a per user home directory to store its keys as well
as
| configuration files. The default home directory is a directory named
"gnupg"
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi John,
some of your questions might be answered by reading README.W32 which you can
find in the doc folder of GnuPG source tarballs:
| GnuPG makes use of a per user home directory to store its keys as well as
| configuration files. The default
I have two instances of GnuPG installed on a Windows 7 OS. I also use an
application that appears to have installed an instance of it for its own use
and put it into one of its separate folders along with some of the files
needed with it, including "gpg.exe" and a unique "gpg.conf" file, among
othe
