From owner-freebsd-security  Tue Jul 13 11:15:40 1999
Delivered-To: freebsd-security@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 998EC150DA
	for <freebsd-security@FreeBSD.ORG>; Tue, 13 Jul 1999 11:15:38 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id LAA79582;
	Tue, 13 Jul 1999 11:15:23 -0700 (PDT)
	(envelope-from dillon)
Date: Tue, 13 Jul 1999 11:15:23 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907131815.LAA79582@apollo.backplane.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: "Allen Smith" <easmith@beatrice.rutgers.edu>,
	Wes Peters <wes@softweyr.com>,
	FreeBSD Security <freebsd-security@FreeBSD.ORG>
Subject: Re: Secure Deletion 
References:  <25695.931889331@critter.freebsd.dk>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


:Just in case anybody wants to do this "RIGHT":
:
:UFS/FFS will issue B_FREEBUF strategy calls, which a device driver
:could turn into "secure delete" operations should the drive support
:this, or multiple over-writes if it doesn't.

    ... and this actually would work.  I use B_FREEBUF in MFS to deallocate
    underlying VM when possible, though I don't bother making it secure.

:phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
:FreeBSD -- It will take a long time before progress goes too far!

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message