From: Milan Broz <mbroz@redhat.com>
To: "Miguel Ángel García Roig" <desarrollo@chillidacompendia.es>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Library to do a 'luksOpen' programatically
Date: Wed, 07 Apr 2010 12:17:53 +0200 [thread overview]
Message-ID: <4BBC5BD1.60209@redhat.com> (raw)
In-Reply-To: <1270634743.2807.37.camel@desa-compendia-tux>
On 04/07/2010 12:05 PM, Miguel Ángel García Roig wrote:
> I haven't physical control to the machine, that's the main problem.
Then there are many others ways how a local attacker can break it anyway.
And if anyone have root account, he can see the encryption key when device
is active.
Milan
next prev parent reply other threads:[~2010-04-07 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 9:12 [dm-crypt] Library to do a 'luksOpen' programatically Miguel Ángel García Roig
2010-04-07 9:54 ` Milan Broz
2010-04-07 10:05 ` Miguel Ángel García Roig
2010-04-07 10:17 ` Milan Broz [this message]
2010-04-07 11:01 ` 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=4BBC5BD1.60209@redhat.com \
--to=mbroz@redhat.com \
--cc=desarrollo@chillidacompendia.es \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox