From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3EE01177.1020503@ameritech.net> From: northern snowfall User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3 MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] Re: some #s References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 5 Jun 2003 22:58:47 -0500 Topicbox-Message-UUID: c5ef047c-eacb-11e9-9e20-41e7f4b1d025 > > >Also, when you reboot your machine, with ctl-alt-del, factotum's pages >are still sitting in memory somewhere. Someone can load their own kernel >and look at the data. I should also change ctl-alt-del to zero out process >memory before bringing the system down. Then there are still crashes... > This was my original point. Rebooting does nothing but obfuscate the issue to a slight extent. Memory leaks are a huge problem, but, can't be evaded by measures that dont cleanse memory in some fashion. As I'm sure we all know here, memory zero'd is pointless in situations where the physical hard- ware can be accessed (even remotely through the kernel or driver bugs, etc). With some slick I/O techniques, nulled memory can still be read for resonating patterns. The only real solution in secure clusters (or other situations) is to force the supervisor code to perform a NSA trusted random-pattern cleanse, or, something more paranoid. But, as is stated above, that doesn't eradicate the problem of crashes. I have some solutions I'm looking at in Autumn, but, the papers wont be out for a while. Though, it probably isn't anything the NIPR/NSA spooks haven't already done ;) Don http://deadchildren.org/~north_ >