On 6/20/05, Ray Percival <[EMAIL PROTECTED]> wrote: > Setting up GPG and I thought I enabled encrypted swap with sysctl -w > vm.swapencrypt.enable=1
You're already there; only GPG doesn't know about that. I suspect you misread the instructions. GPG will whine about insecure memory so long as it does not have setuid bits set on the executable. By encrypting the swap, you eliminated the need for those setuid bits. GPG, however, will continue to whine until you either tell it to shut up or add the (now unnecessary) setuid bits. Your gpg.conf is the place to edit and add the equivalent of the command line option "--no-secmem-warning" to your setup. Cheers, Rogier -- If you don't know where you're going, any road will get you there.
