From owner-freebsd-security Thu Nov 18 14: 1:50 1999 Delivered-To: freebsd-security@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 2596915478 for ; Thu, 18 Nov 1999 14:01:46 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id OAA21232; Thu, 18 Nov 1999 14:00:31 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id OAA03794; Thu, 18 Nov 1999 14:00:30 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA22856; Thu, 18 Nov 99 14:00:28 PST Message-Id: <383476FB.CAAB1A0E@softweyr.com> Date: Thu, 18 Nov 1999 15:00:27 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: trouble@netquick.net Cc: Barrett Richardson , David G Andersen , freebsd-security@FreeBSD.ORG, Greg Lehey Subject: Re: secure filesystem wiping References: <3833923C.10A7208F@netquick.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org TrouBle wrote: > > i appreciate all the help, but this is not what im looking for... i want > to WIPE freespace on the disk > > obliterate only wipes the one file you specify.. i want to wipe all the > free space on the disk, without damaging good intact files on it, linux > has a progrtam called wipe that does this, now ill ask again is there > something similiar for freebsd You've got me thinking about this now, it would be a neat tool to run over your disks in daily or weekly. It would be pretty straightforward to run over a slice on block at a time, checking to see if it is allocated and obliterating the blocks that are not. Problem is, I don't know how you could do this on a mounted filesystem; is it possible to lock the file allocation long enough to zap the block? Pointers to helpful filesystem hackery and/or knowlegable hackers appreciated. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message