using insecure memory

Chris Hilts
Fri, 15 Oct 1999 22:05:42 +0000

Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 15, 1999 at 07:00:47PM -0500, Derek Moeller wrote:

> As far as I know, the problem arose because a non-root user does not
> have permissions to manipulate memory in the way gnupg would need to
> in order to secure memory. Correct me if I'm wrong, but I don't
> believe there are any compile-time options available to outsmart
> system security.
Just make your binary setuid root. (as root: chmod u+s `which gpg`) This will allow gpg to lock memory. Chris --=20 "#define QUESTION ((bb) || !(bb)) - Shakespeare." --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: For info see iD8DBQE4B6U1qn4IuHG5mmkRATGwAJ4qzwpWhs0g3/Yxfqukksd7dlBczwCfZuwq gBn42rSa9ZQ26/RAkvf2Y/w= =/1iq -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD--