I am using Gpg 2.0.17 in Windows. Am I correct in saying that the options
file, if one existed, should be located in the home directory, i.e.,
%homepath%\appdata\roaming\gnupg, that it should be named options, and that
it would be utilized automatically by the gpg program whenever commands are
On 10/09/12 22:46, Landon Hurley wrote:
Maybe some sort of hood made out of wire mesh to stop radiation leakage.
Ah, you mean a tinfoil hat? ;P
Peter.
--
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is
On 09/10/2012 04:55 PM, Robert J. Hansen wrote:
Second, no, of course the distro-on-a-stick doesn't defend against Van
Eck phreaking.
Distro-on-a-stick doesn't defend against anything if you don't trust the
hardware, which you shouldn't if you don't trust the software. It's
entirely
On 10/09/12 19:45, ved...@nym.hush.com wrote:
Either people are on their own computers, which they trust, and
which they can cleanse the memory and reboot, or they are on
untrusted computers, where memory is the least of their problems.
I think people want it because editing a text file
On 09/09/12 23:29, Marco Steinacher wrote:
Isnt't that the problem with almost any data? At some point you have to
decrypt it to edit or view it with some application.
[...]
I think demanding all allplications to be aware of this and to handle it
securely is quite a strong requirement,
On 11/09/12 09:12, John A. Wallace wrote:
I am using Gpg 2.0.17 in Windows. Am I correct in saying that the options
file, if one existed, should be located in the home directory, i.e.,
%homepath%\appdata\roaming\gnupg
You can see what the home directory of GnuPG is with the command
gpgconf
, that it should be named options
Oh, wait, no. I think you're supposed to name it gpg.conf, and that options is
some sort of legacy name that is also accepted? gpg.conf is the normal file you
would use to store your configuration, I know that for sure.
Peter.
--
I use the GNU Privacy Guard
On 11/09/12 16:57, Heinz Diehl wrote:
You can mount /tmp and the various other tmpfiles to memory. That's
what I do (not for security reasons, but to have the tmp stuff deleted
on reboot).
So you store the unencrypted file to /tmp and edit it there with whatever
program is needed? Say you're
On Di, Sep 11 2012, Peter Lebbing wrote:
I think people want it because editing a text file *now* might
expose the data *far into the future*. Temp files and swap pages
have the potential to live on your hard disk for a very long time.
[...]
The only sure-fire remedy against a temp file that
On 11/09/12 16:58, Jens Lechtenboerger wrote:
Instead, I'm using full disk encryption.
I also have an OS on full disk encryption (not my regular workstation OS). I
still see a use for a safe text editor, for example as a lightweight
alternative to FDE.
Peter.
--
I use the GNU Privacy Guard
On 11.09.2012, Peter Lebbing wrote:
The only sure-fire remedy against a
temp file that got deleted is a full wipe of the partition the file was on, as
far as I know.
You can mount /tmp and the various other tmpfiles to memory. That's
what I do (not for security reasons, but to have the tmp
11 matches
Mail list logo
