Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!cbosgd!ukma!ukecc!edward
From: edward@ukecc.UUCP (Edward C. Bennett)
Newsgroups: net.sources.bugs
Subject: Re: What happens during an unlink(2)
Message-ID: <438@ukecc.UUCP>
Date: Sun, 4-May-86 21:01:53 EDT
Article-I.D.: ukecc.438
Posted: Sun May  4 21:01:53 1986
Date-Received: Thu, 8-May-86 21:06:28 EDT
References: <947@kitty.UUCP> <403@ukecc.UUCP> <979@kitty.UUCP> <422@ukecc.UUCP> <238@chronon.chronon.UUCP>
Organization: Univ. of Ky. Engineering Computing Center
Lines: 26
Keywords: Disk blocks sometimes get zeroed

In article <238@chronon.chronon.UUCP>, eric@chronon.UUCP (Eric Black) writes:
> >
> >	[discussion of what unlink(2) does]
> 
> Some unitory systems do, indeed, zero out disk blocks when de-allocated,
> and similarly clear memory when freed.  Any system you sell to customers
> with concerns about security will require this.  Check out DOD requirements
> for secure systems in the "Department of Defense Trusted Computer
> System Evaluation Criteria", publication CSC-STD-001-83 (my copy is
> dated March 1985) for this and other interesting features...
> 
> Spooks aren't the only people who might desire disks & memory to be
> cleansed when released, by the way.
> 

	You're absolutely right. I never though about that way.

-- 
Edward C. Bennett

UUCP: ihnp4!cbosgd!ukma!ukecc!edward

Kentucky: The state that is being dragged, kicking and screaming,
	  into the 20th century.

"Goodnight M.A."