All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Possibility for safe Luks partition delete functionality
Date: Wed, 11 Dec 2013 22:48:16 +0100	[thread overview]
Message-ID: <20131211214816.GA9509@fancy-poultry.org> (raw)
In-Reply-To: <20131211202151.GA15640@tansi.org>

On 11.12.2013, Arno Wagner wrote: 

> Wit things like rubber-hise cryptoanalysis, you can still get
> at it. If the header is wiped, that becomes impossible.

Of course. You will then have the possibility to maybe safe your life
by giving the passphrase to the adversary, which would be impossible
if the header has been wiped.

In all other situations, simply cutting the power will be the fastest
way to secure your data in case of an "emergency".

It all boils down to the fact that WDE is very suitable to protect
your data in case a laptop gets stolen or a harddisk dies, but not
against criminal minds putting a threat on your life.

Furthermore, with solid state drives taking over the market, WDE
renders all of their advantages (high speed and low access time) to
zero.

Just my 5ø.

  reply	other threads:[~2013-12-11 21:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 18:59 [dm-crypt] Possibility for safe Luks partition delete functionality tada
2013-12-11 19:16 ` Heinz Diehl
2013-12-11 19:18   ` Heinz Diehl
2013-12-11 20:21     ` Arno Wagner
2013-12-11 21:48       ` Heinz Diehl [this message]
2013-12-11 22:53         ` Arno Wagner
2013-12-12  6:11           ` Heinz Diehl
2013-12-11 20:55   ` Matthias Schniedermeyer
2013-12-11 23:22     ` Sven Eschenberg
2013-12-12  0:29       ` Matthias Schniedermeyer
2013-12-12  0:49         ` Arno Wagner
2013-12-15  2:55     ` Robert Nichols
2013-12-15 12:47       ` Arno Wagner

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=20131211214816.GA9509@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --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.