moeller at dophnic
Oct 15, 1999, 5:00 PM
Post #5 of 6
On Fri, Oct 15, 1999 at 03:43:08PM -0700, nytshade [at] mail 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
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, nytshade [at] mail wrote:
> > > 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 :)
> > Put:
> > no-secmem-warning
> > in your ~/.gnupg/options file.
moeller [at] dophnic