All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] (OT) Secure data wipe
Date: Sun, 9 Dec 2012 17:18:15 +0100	[thread overview]
Message-ID: <20121209161815.GA17603@tansi.org> (raw)
In-Reply-To: <20232.77.109.139.26.1355052014.squirrel@lavabit.com>

Sent the my original reply by accident only to the OP. Here
a copy for the list:

I comment on this in the cryptsetup FAQ in items 5.4, 5.5 and 5.19.
For the case of a non-LUKS container, the current state-of-the-art
is that for HDDs a single pass of zeros is enough and for any type
of non-valitele memory (SSD, USB-key, etc.) it is unclear. In all
cases encryption helps. Defect management may complicate things for
HDDs and SSDs, but for HDDs you can at least query the reallocated
count in teh SMART status to see whether that happened.

As to swap, you can either disable it or use encrypted swap,
possibly with an one-tile boot-up key, and, if you like
frequent key-changes.

You can only secure-delete a single file if you understand what
your filesystem does. The thing you have heard is complete
nonsense though. One way with some filesystems is to overwrite
the original file. The Linux tool "wipe" does that. It is
insecure with ext3 (data may be in the log) btrfs (later writes
may not go to the same sectors) and others. You can delete the
file and overwtite all empty space, but that may leave some
leftovers.

As to papers, for HDDs, look at the original Gutman paper and its
adendum:
http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html

For SSDs, look at
http://www.usenix.org/events/fast11/tech/full_papers/Wei.pdf
and possibly its references.

Arno

On Sun, Dec 09, 2012 at 06:20:14AM -0500, jugree@lavabit.com wrote:
> Hello.
> 
> How to securely delete data from a hard drive? Is it possible without
> physical destruction?
> 
> How to work with sensitive data if you're using swap? Is it enough to
> run `swapoff', decrypt some data, encrypt it again, and run `swapon'?
> 
> Is it possible to securely delete a single file? I've heard that you
> should create another file with the same name, write some data to it,
> and delete it.
> 
> This is a popular topic, but it's really hard to find any proofs.
> 
> Can you suggest any books or papers on the subject?
> 
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell

  parent reply	other threads:[~2012-12-09 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 11:20 [dm-crypt] (OT) Secure data wipe jugree
2012-12-09 12:26 ` Javier Juan Martínez Cabezón
2012-12-09 14:48   ` Karol Babioch
2012-12-09 15:49     ` Javier Juan Martínez Cabezón
2012-12-09 16:38     ` Arno Wagner
2012-12-09 14:55 ` Karol Babioch
2012-12-09 16:18 ` Arno Wagner [this message]
2012-12-11  8:39 ` Roscoe

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=20121209161815.GA17603@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /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.