Date: Sat, 22 May 1999 17:11:38 +0200 From: Eivind Eklund <eivind@FreeBSD.ORG> To: Thomas Valentino Crimi <tcrimi+@andrew.cmu.edu> Cc: brooks@one-eyed-alien.net, Dag-Erling Smorgrav <des@flood.ping.uio.no>, "Ilmar S. Habibulin" <ilmar@ints.ru>, posix1e@cyrus.watson.org, freebsd-security@FreeBSD.ORG Subject: Re: secure deletion Message-ID: <19990522171138.K85583@bitbox.follo.net> In-Reply-To: <YrFPJUy00Uw_0f9WY0@andrew.cmu.edu>; from Thomas Valentino Crimi on Fri, May 21, 1999 at 03:34:56PM -0400 References: <xzpwvy2pax2.fsf@localhost.ping.uio.no> <Pine.GSO.4.05.9905211100050.6166-100000@orion.ac.hmc.edu> <19990521201043.I85583@bitbox.follo.net> <YrFPJUy00Uw_0f9WY0@andrew.cmu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 21, 1999 at 03:34:56PM -0400, Thomas Valentino Crimi wrote: > Excerpts from mail: 21-May-99 Re: secure deletion by Eivind Eklund@FreeBSD.OR > > Either tunefs or chflags - it would be relatively expensive, so if you > > only need it for some data, it is probably better to have more > > fine-grained control than per-FS. > > Might I also suggest a 'normal' user option for one particular file to > be securely wiped? It is not possibly to securely delete a file after data has been written to it unless the wish to do so has been indicated to the kernel from the start of the file's life time. We do de-fragmentation while the FS is running (or at least that's what I understood the dorealloc code to do). Eivind. 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?19990522171138.K85583>