Date: Sun, 18 Jun 2006 22:41:10 +0200 From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "Nick Borisov" <neiro21@gmail.com> Cc: freebsd-security@freebsd.org Subject: Re: memory pages nulling when releasing Message-ID: <86k67eryc9.fsf@xps.des.no> In-Reply-To: <3bcb4e3f0606181309h70c08dc6l691bbb6e5b48615a@mail.gmail.com> (Nick Borisov's message of "Mon, 19 Jun 2006 00:09:57 %2B0400") References: <3bcb4e3f0606180056o63424cc0g5c121443e45fa333@mail.gmail.com> <3bcb4e3f0606180127m3c4fdb13n2b42deb881b7bdc6@mail.gmail.com> <86odwqs71f.fsf@xps.des.no> <3bcb4e3f0606181309h70c08dc6l691bbb6e5b48615a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Nick Borisov" <neiro21@gmail.com> writes: > Well, providing zeroed pages to processes is not quite similar to > explicit cleaning of pages after use as some security standards > demand. That's why I'm asking. The "Z" malloc option seems to be > suitable but it's actually for debugging. Which security standard requires that one part of a process protect itself from another part of the same process? malloc() operates entirely in userland and is entirely replacable; there are plenty of malloc() implementations available both in ports and other places. If you're worried about authentication tokens and the like, our PAM library and modules zero memory used to store authentication data when it is released. So does OpenSSH. If this does not satisfy you, you're going to have to quote the relevant security standards, because it is not clear to me what you want, and I get the feeling that you don't quite know yourself. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k67eryc9.fsf>