Date: Thu, 20 May 1999 18:21:42 -0700 From: Eric Lakin <elakin@ricochet.net> To: Avalon Books <avalon@advicom.net> Cc: security@FreeBSD.ORG Subject: Re: Secure Deletion Message-ID: <19990520182142.A1242@ptah.ricochet.net> In-Reply-To: <Pine.BSF.4.05.9905201452520.2841-100000@vespucci.advicom.net>; from Avalon Books on Thu, May 20, 1999 at 03:05:18PM -0500 References: <3.0.6.32.19990520095507.00840010@india.wind-river.com> <Pine.BSF.4.05.9905201452520.2841-100000@vespucci.advicom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990520182142.A1242>