using insecure memory

Derek Moeller
Fri, 15 Oct 1999 19:00:47 -0500

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

On Fri, Oct 15, 1999 at 03:43:08PM -0700, wrote:

> er.. That's not exactly what I was hoping for.. is there any way to
> actualy make it STOP using insecure memory instead of just making the
> errors go away? are there any compile options or such?
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. I don't believe you'd see that message under root, since it would have sufficient permissions at that point.
> On Fri, 15 Oct 1999, Derek Moeller wrote:
> > On Fri, Oct 15, 1999 at 02:47:08PM -0700, wr=
> > > Folx,
> > > How do I get my binary to stop "using insecure memory"? I looked
> > > through the docs, and they mentioned the error, but didn't give any
> > > directions on how to fix it :)
> >=20
> > Put:
> > no-secmem-warning
> > in your ~/.gnupg/options file.
--=20 Derek Moeller --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: For info see iD8DBQE4B8AvRmWqWATp64gRAUO8AKCmdRcdcKEKdXejy5KHbThMWWsyZgCg5XDT Ro3vrQlrfBWw5qVvQs3WAMs= =rjPl -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7--