From owner-freebsd-security Thu May 20 18:23:24 1999 Delivered-To: freebsd-security@freebsd.org Received: from ptah.ricochet.net (mg-206191146-151.ricochet.net [206.191.146.151]) by hub.freebsd.org (Postfix) with ESMTP id 976A6158D8 for ; Thu, 20 May 1999 18:23:16 -0700 (PDT) (envelope-from elakin@ricochet.net) Received: (from elakin@localhost) by ptah.ricochet.net (8.9.3/8.9.2) id SAA32989; Thu, 20 May 1999 18:21:45 -0700 (PDT) (envelope-from elakin) Date: Thu, 20 May 1999 18:21:42 -0700 From: Eric Lakin To: Avalon Books Cc: security@FreeBSD.ORG Subject: Re: Secure Deletion Message-ID: <19990520182142.A1242@ptah.ricochet.net> Reply-To: elakin@ricochet.net References: <3.0.6.32.19990520095507.00840010@india.wind-river.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Avalon Books on Thu, May 20, 1999 at 03:05:18PM -0500 X-Disclaimer: Yow! Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 20, 1999 at 03:05:18PM -0500, Avalon Books spread the following propaganda: > > > As for "secure" deletion... Why doesn't someone just write a simple > > user-space program to do that. True, it wouldn't handle calls to unlink(), > > but one would think that someone could modify the library really quick > > (provided no one does a system call directly, but uses the libc interface > > instead). I think this would be much better for everyone involved. > > Actually, I've done this already. At the moment, its a simple > stand-alone program (I originally wrote during my DOS days, years ago), > but I've been toying with the idea of adding the method in as an option > for 'rm'. No need to tie up the kernel with this sort of thing. > > It uses a combination of randomly-generated and pattern-specific > overwrites of a file (or group of files) in-place, in order to make > recovery extremely difficult--even with advanced equipment (like > echo-cancellation analysis systems). A standard file-deletion is issued > after its done mangling the file(s) in question. It works ok, I guess, as > betas go. This sounds similar to "rm -P" in a stock FreeBSD system (3.1, atleast) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message