From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] distributing a linux disk crypted with dm-crypt
Date: Wed, 19 Aug 2009 17:42:34 +0200 [thread overview]
Message-ID: <87tz03lsid.wl%htd@fancy-poultry.org> (raw)
In-Reply-To: <1250693664.4a8c1220018bf@webmail.inmano.com>
At Wed, 19 Aug 2009 16:54:24 +0200,
octane indice wrote:
> But every people I give the appliance will have the crypto key which crypt
> and decrypt data. So, as a security point of view, it's not acceptable.
I'm not shure at all if I understand correctly what you have in mind, but
to unlock a LUKS/dmcrypt partition, you have to provide the correct passphrase/keyfile.
If you do not, there is no way other than bruteforcing it or an attack towards the
encryption itself. The master key itself stays fully encrypted.
You can read more here:
http://cryptsetup.googlecode.com/svn-history/r42/wiki/LUKS-standard/on-disk-format.pdf
next prev parent reply other threads:[~2009-08-19 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 14:54 [dm-crypt] distributing a linux disk crypted with dm-crypt octane indice
2009-08-19 15:42 ` Heinz Diehl [this message]
2009-08-19 16:00 ` Sam
2009-08-20 10:27 ` octane indice
2009-08-19 16:08 ` Moji
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=87tz03lsid.wl%htd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox