From owner-freebsd-security  Tue Oct 14 17:46:51 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA00831
          for security-outgoing; Tue, 14 Oct 1997 17:46:51 -0700 (PDT)
          (envelope-from owner-freebsd-security)
Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA00817
          for <security@FreeBSD.ORG>; Tue, 14 Oct 1997 17:46:44 -0700 (PDT)
          (envelope-from mike@word.smith.net.au)
Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id KAA00590;
	Wed, 15 Oct 1997 10:13:31 +0930 (CST)
Message-Id: <199710150043.KAA00590@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Wes Peters <softweyr@xmission.com>
cc: Terry Lambert <tlambert@primenet.com>, security@FreeBSD.ORG
Subject: Re: C2 Trusted FreeBSD? 
In-reply-to: Your message of "Tue, 14 Oct 1997 10:01:37 CST."
             <199710141601.KAA10425@obie.softweyr.ml.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 Oct 1997 10:13:31 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> There are no incidences in which pages are returned to you with previous
> random cruft left in them?

There shouldn't be, no.

> And besides, zero-filling memory isn't sufficient, it has to be
> overwritten a number of times to make sure now residual information can
> be obtained.  These standards date back to core and even mercury-wire
> memory.  Yes, I've actually worked with computers that feature *both* in
> my career.  ;^)

If you can suggest how one goes about obtaining "residual" information 
from a saturated logic device in a synchronous memory subsystem, I'd be 
very interested in hearing it.

Or is this more specification paranoia?

mike