On Fri, Sep 10, 1999 at 08:19:27PM +0200, E Forrest Carpenter wrote:
> gpg: Warning: using insecure memory!
> Press any key to continue...
>
> Anyone know if there's a flag I'm missing or something to make this
> output go away?
echo no-secmem-warning >> ~/.gnupg/options
--
Jos Backus
On Fri, Sep 10, 1999 at 02:29:38PM -0400, Pete Toscano wrote:
> set the SUID bit on the gpg binary. the problem is -- so the gpg docs
> go -- that, unless the program is being run as root, it could be swapped
> out of memory and then, anyone who can read the swap device might be
> able to get you
set the SUID bit on the gpg binary. the problem is -- so the gpg docs
go -- that, unless the program is being run as root, it could be swapped
out of memory and then, anyone who can read the swap device might be
able to get your password. now, if you have permissions on your swap
device set so t
I realize this isn't the most appropriate forum to ask this question,
but I have a feeling someone here knows the answer and might respond
quickly. Everytime I send a message that's signed with GPG, I get the
following output, and need to hit a character to return to mutt and
actually send the me
