Date: Fri, 1 Feb 2002 13:52:44 +0100 From: "Thomas E. Zander" <riggs@hadiko.de> To: Dimitry Andric <dim@xs4all.nl> Cc: ports@freebsd.org Subject: Re: gnupg insecure memory Message-ID: <20020201125244.GA59129@f113.hadiko.de> In-Reply-To: <62348859333.20020201130554@xs4all.nl> References: <20020131110513.GE46820@f113.hadiko.de> <20020131111203.A15F63FC05@energyhq.homeip.net> <20020131112001.GF46820@f113.hadiko.de> <20020131185306.A79863@graf.pompo.net> <20020131192316.GA46654@voi.aagh.net> <62348859333.20020201130554@xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Fri, 01. Feb 2002, at 13:05 +0100, Dimitry Andric wrote according to [Re: gnupg insecure memory]: > On 1/31/2002 at 20:23:16 Thomas Hurst wrote: > > TH> It's fine here on -PRERELEASE as of about 40 days ago. > > I have no idea why it did work on -PRERELEASE. Maybe the super-user > requirement was just added to mlock(2) recently? In my first mail I explicitly made clear that the mlock() problem of gpg is affected to the super-user, too (in 4.5-R). By the way, it would be awesomely useless to give mlock() funcionality to every user... Regards, Riggs -- - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. ---- "It committed suicide." said Marvin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020201125244.GA59129>