All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Rosemann <heiko.rosemann@web.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS self-destruct key
Date: Mon, 31 Mar 2014 22:51:15 +0200	[thread overview]
Message-ID: <5339D543.20006@web.de> (raw)
In-Reply-To: <20140331221752.42935543@burger.lunch.za.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/31/2014 10:17 PM, Andrew wrote:
> On Mon, 31 Mar 2014 15:06:12 +0200 Arno Wagner <arno@wagner.name>
> wrote:
>> On Mon, Mar 31, 2014 at 14:19:29 CEST, Andrew wrote: [...]
>>> I read the thread -- interesting reading (Gmane seems a little
>>> off for me at the moment though.)
>>> 
>>> A few points that were not raised directly by anyone are:
>>> 
>>> * Some of the worst attackers *do* lack technical skills.
>>> While various interest groups do have technical experts, less
>>> skilled persons may try their hand first, and succeed in
>>> destroying the evidence.  Terrorism has lately tended towards a
>>> cell structure.  A particular cell may not have access to
>>> adequate technical resources, while not lacking "skills" like
>>> kidnapping, robbery and torture of those they target.
>> 
>> Even the dumbest attackers have seen the movies where the magic 
>> computer destroys all data when the wrong password is entered.
> This is not true.

Well, the number of attackers which is knowledgeable enough to detect
a luks device and figure out that they need a password to open it (or
stupid enough to just type a password at an unknown prompt), but not
knowledgeable enough to make a backup before trying is probably
insignificant, I'm even leaning towards zero.

>> And when you come to any writing about compouter forensics, the
>> first rule is always to never work on originals.
> This is not relevant.

Yes it is. Because it's not only in any writing but also common sense.

If the attacker works on a backup and still has the original,
destroying the backup does not help anybody. This is what renders all
your further points moot.

I can see exactly one use case for a "destroy password" and that has
been discussed in the thread mentioned above and all the neccessary
tools have been implemented in the form of the luksErase command. In
short: The data is more valuable than your life _and_ you have a few
seconds of time on your computer _before_ the attacker takes control
over it. You could implement it in such a way as the machine looks for
a key on a USB stick and if none is found, runs luksErase instead of
luksOpen, or by booting from a USB stick with a working system but
when booting from the HDD (when the USB stick is missing) it runs
luksErase.

Best Regards,
Heiko

- -- 
eMails verschlüsseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlM51UAACgkQ/Vb5NagElAVcvACbByshRHJm5r1GqO1zen0vx9t3
8HkAnRJAhxXrLru6JuKbuVkjDK8RrgD6
=jspl
-----END PGP SIGNATURE-----

      reply	other threads:[~2014-03-31 20:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  5:17 [dm-crypt] LUKS self-destruct key Andrew
2014-03-31  7:03 ` Chris Drake
2014-03-31  9:35 ` Arno Wagner
2014-03-31  9:52 ` Jonas Meurer
2014-03-31 12:19   ` Andrew
2014-03-31 13:06     ` Arno Wagner
2014-03-31 20:17       ` Andrew
2014-03-31 20:51         ` Heiko Rosemann [this message]

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=5339D543.20006@web.de \
    --to=heiko.rosemann@web.de \
    --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.