Date: Mon, 19 Jun 2006 00:09:57 +0400 From: "Nick Borisov" <neiro21@gmail.com> To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" <des@des.no>, freebsd-security@freebsd.org Subject: Re: memory pages nulling when releasing Message-ID: <3bcb4e3f0606181309h70c08dc6l691bbb6e5b48615a@mail.gmail.com> In-Reply-To: <86odwqs71f.fsf@xps.des.no> References: <3bcb4e3f0606180056o63424cc0g5c121443e45fa333@mail.gmail.com> <3bcb4e3f0606180127m3c4fdb13n2b42deb881b7bdc6@mail.gmail.com> <86odwqs71f.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
2006/6/18, Dag-Erling Sm=F8rgrav <des@des.no>: > "Nick Borisov" <neiro21@gmail.com> writes: > > Could you tell me if FreeBSD supports memory page nulling when > > releasing it to prevent unauthorized access to data left in the page > > after it's allocated again. > > Processes always get zeroed pages from the kernel. This is the case > for all Unices, and has been for decades. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bcb4e3f0606181309h70c08dc6l691bbb6e5b48615a>