Date: Thu, 31 Jan 2002 12:20:01 +0100 From: "Thomas E. Zander" <riggs@hadiko.de> To: ports@freebsd.org Subject: Re: gnupg insecure memory Message-ID: <20020131112001.GF46820@f113.hadiko.de> In-Reply-To: <20020131111203.A15F63FC05@energyhq.homeip.net> References: <20020131110513.GE46820@f113.hadiko.de> <20020131111203.A15F63FC05@energyhq.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Thu, 31. Jan 2002, at 12:11 +0100, Miguel Mendez wrote according to [Re: gnupg insecure memory]: > This is totally normal behavior. Insercure memory means that the pages that > contain you private key data might get swapped. In order to avoid this they > need to be marked as non-swappable (don't remember the exact term, sorry) and > only setuid programs can do it if you run them as a normal user. Not a big > issue I think. I know about the memory locking thing, but normally (I am using gpg for about 2 years) you do a chmod u+s being root and this is the whole thing. And this mechanism doesn't work since the upgrade to 4.5-RELEASE, so I want to figure out, why. 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?20020131112001.GF46820>