Date: Fri, 1 Feb 2002 13:05:54 +0100 From: Dimitry Andric <dim@xs4all.nl> To: Thomas Hurst <tom.hurst@clara.net> Cc: ports@freebsd.org Subject: Re: gnupg insecure memory Message-ID: <62348859333.20020201130554@xs4all.nl> In-Reply-To: <20020131192316.GA46654@voi.aagh.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/31/2002 at 20:23:16 Thomas Hurst wrote:
TH> Isn't this more a question of why gpg is failing to mlock()?
Because you are not running it as root, perhaps? According to
mlock(2):
These calls are only available to the super-user.
So if I run gpg as root, it gives no security warning.
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?
Cheers,
- --
Dimitry Andric <dim@xs4all.nl>
PGP Key: http://www.xs4all.nl/~dim/dim.asc
Fingerprint: 7AB462D2CE35FC6D42394FCDB05EA30A2E2096A3
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5i
Comment: http://www.gn.apc.org/duncan/stoa_cover.htm
iQA/AwUBPFp2l7BeowouIJajEQJkKgCfbLu/SDKkNzQYGKmJ0bY7C/9JY+YAoM/O
JajWYJEvrNolAxvcQvvt1gKZ
=IkMz
-----END PGP SIGNATURE-----
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?62348859333.20020201130554>