From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Possibility for safe Luks partition delete functionality
Date: Wed, 11 Dec 2013 21:21:51 +0100 [thread overview]
Message-ID: <20131211202151.GA15640@tansi.org> (raw)
In-Reply-To: <20131211191816.GB9082@fancy-poultry.org>
On Wed, Dec 11, 2013 at 20:18:16 CET, Heinz Diehl wrote:
> On 11.12.2013, Heinz Diehl wrote:
>
> > You can do that easily by running dd against the first MB's of the
> > respective partition..
>
> I forgot: you can just switch off the power, which will surely be
> much faster than wiping the LUKS header.
Ah, no? Unless you have it in a RAM-disk? If you power off,
the device is not mapped anymore, but the header is there.
Wit things like rubber-hise cryptoanalysis, you can still get
at it. If the header is wiped, that becomes impossible.
Arno
--
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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-12-11 20:21 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 [this message]
2013-12-11 21:48 ` Heinz Diehl
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=20131211202151.GA15640@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.