All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS/dm-crypt vulnerable?
Date: Mon, 10 Aug 2009 08:12:46 +0200	[thread overview]
Message-ID: <20090810061245.GA9508@maude.comedia.it> (raw)
In-Reply-To: <20090808153635.GA31434@fancy-poultry.org>

On Sat, Aug 08, 2009 at 05:36:35PM +0200, Heinz Diehl wrote:
>But what happens when the machine is powered off and stolen?
>The thief wants to have my data. Can he/she use something like "stoned" to
>get into the system and decrypt the harddisk contents?
To achieve this, they will have to hand it back, wait for you to type
your password to boot, then steal it again :P

Stoned is just a trojan that installs into the boot sector,
a very well done trojan, but that is.
The whole argument about stoned and truecrypt is that stoned developer
insisted truecrypt was not secure, because it did not enforce checking
of boot sector integrity.
Truecrypt developers said that was a moot point, because, if someone is
able to replace the boot sector it could well replace the code that
checks its integrity.

add a bit of hype, mix .....

L.

-- 
Luca Berra -- bluca@comedia.it
         Communication Media & Services S.r.l.
  /"\
  \ /     ASCII RIBBON CAMPAIGN
   X        AGAINST HTML MAIL
  / \

  parent reply	other threads:[~2009-08-10  6:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 13:26 [dm-crypt] LUKS/dm-crypt vulnerable? Heinz Diehl
2009-08-08 14:54 ` Marc Ballarin
2009-08-08 15:15   ` Michael Gebetsroither
2009-08-08 15:40     ` Heinz Diehl
2009-08-08 16:23       ` Michael Gebetsroither
2009-08-08 16:47         ` Heinz Diehl
2009-08-08 15:36   ` Heinz Diehl
2009-08-09 20:15     ` markus reichelt
2009-08-10  6:12     ` Luca Berra [this message]
2009-08-10  7:10       ` Heinz Diehl
2009-08-10  8:13         ` Sven Eschenberg
2009-08-10 10:28         ` Marc Ballarin
2009-08-10 10:34           ` Michael Gebetsroither
2009-08-10 12:47             ` Arno Wagner
2009-08-10 12:29           ` Heinz Diehl
2009-08-08 15:23 ` Arno Wagner
2009-08-08 17:26   ` Heinz Diehl

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=20090810061245.GA9508@maude.comedia.it \
    --to=bluca@comedia.it \
    --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.