All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: secure erasure of files?
Date: Wed, 13 Feb 2002 10:27:41 -0800	[thread overview]
Message-ID: <20020213182741.GA335@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0202121409150.18597-100000@mustard.heime.net> <Pine.LNX.4.33.0202121438560.7616-100000@unicef.org.yu> <20020212165504.A5915@devcon.net> <3C6A32ED.755159F3@aitel.hist.no>
In-Reply-To: <3C6A32ED.755159F3@aitel.hist.no>

On Wed, Feb 13, 2002 at 10:33:33AM +0100, Helge Hafting wrote:
> Andreas Ferber wrote:
> 
> > I don't know if any filesystem currently relocates blocks if you
> > overwrite a file, but it's certainly possible and allowed (everything
> > else except the filesystem itself simply must not care where the data
> > actually ends up on the disk).
> > 
> A log-structured fs will write new blocks everytime, afaik.

Ext3 only does that on truncate in ordered/writeback mode and probably in
data journaling mode too.

> Ext3 with data journalling keeps copies of recently written data
> in the journal.  Now, if you create a "secret" file and then overwrite
> it you'll still find a copy in the journal until the journal wraps
> It may not wrap if the next thing you do is umount/shutdown.
>
> A secure rm must know the fs it works with.  A better solution
> is to overwrite the entire partition with garbage. The only
> perfect way is to destroy the magnetic surfaces though.
>

Yep, very true.

Phycally breaking the drive apart into pieces and then burning should
suffice. 

Mike

  reply	other threads:[~2002-02-13 18:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 13:12 secure erasure of files? Roy Sigurd Karlsbakk
2002-02-12 13:41 ` Davidovac Zoran
2002-02-12 14:03   ` Padraig Brady
2002-02-12 15:55   ` Andreas Ferber
2002-02-12 19:47     ` Jan Hudec
2002-02-12 20:25       ` Andrew Morton
2002-02-13  0:03         ` Jeff Garzik
2002-02-13  9:33     ` Helge Hafting
2002-02-13 18:27       ` Mike Fedyk [this message]
2002-02-13  0:36 ` Tom Vier
2002-02-13  0:45   ` Jeff Garzik
2002-02-20 15:34 ` Bill Davidsen
     [not found] <200202121326.g1CDQct12086@Port.imtp.ilyichevsk.odessa.ua>
2002-02-12 13:33 ` Roy Sigurd Karlsbakk
2002-02-17 21:19   ` Jan-Frode Myklebust
2002-02-19 12:54     ` Jens Schmidt
2002-02-19 14:24       ` Richard B. Johnson
2002-02-21  2:56         ` Petro
2002-02-21  3:20           ` M. Edward Borasky
2002-02-21 17:01             ` Holger Lubitz
2002-02-26  3:39             ` Petro
  -- strict thread matches above, loose matches on Subject: below --
2002-02-12 21:14 Torrey Hoffman
2002-02-19 14:48 Roy Sigurd Karlsbakk
2002-02-19 17:32 ` Rogier Wolff
2002-02-19 17:59   ` Martin J. Bligh
2002-02-19 18:48     ` Rogier Wolff
2002-02-19 20:01       ` Andreas Dilger
2002-02-19 23:13 ` Roy Sigurd Karlsbakk
2002-02-19 16:19 Jesse Pollard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020213182741.GA335@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.