[cc: list trimmed]

On Sun, Dec 12, 1999 at 01:24:17AM -0600, Peter Samuelson wrote:

> And, in general, any time you want the file *gone* more than you want
> it *unlinked*.  If you don't have write access to the directory, for
> example, -T will at least truncate the file.
> 
> I thought about a companion flag to zero the file contents, for a
> similar effect except that the file will no longer be accessible even
> reading the raw block device.  Not a very strong security measure:
[..]

fileutils seems to include something called shred(1):

NAME
       shred  -  delete  a file securely, first overwriting it to
              hide its contents
[..]
       -u, --remove
                     truncate and remove file after overwriting

-- 
        "Damn and blast British Telecom!" exclaimed Dirk, the words
coming easily from force of habit.

Reply via email to