DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Lefebvre <alto.spam@laposte.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Questions about LUKS / LVM
Date: Mon, 19 Sep 2011 18:11:51 +0200	[thread overview]
Message-ID: <4E7769C7.5040805@laposte.net> (raw)
In-Reply-To: <1316448000.17657.3@mofo>

On 19/09/2011 18:00, Karl O. Pinc wrote :
> On 09/19/2011 10:45:52 AM, Robbie Smith wrote:
> 
>> How much of a load on the system would LUKS + LVM be? Is it
>> likely to result in a noticeable drop in performance?
> 
> It all depends, but generally no because cpu is _so_ much
> faster than disk these days.

Indeed, you won't notice it on a modern computer, especially for every
day use. It may be painful for data transfer from one encrypted disk to
another encrypted disk, but you can expect very good rates anyway. It
depends on the cipher you use, on your machine, ...

>> Does entering the key(s) at boot decrypt the whole volume,
>> or just provide a means for the kernel module
>> to decrypt and encrypt on-the-fly?
> 
> The latter.
> 
>> And… how does it work? The documentation makes mention of multiple
>> key-slots; but I'm a little baffled as to how different keys can be
>> used to decrypt the same volume. It is based on symmetric
>> cryptography isn't it?
> 
> Yes, but the master key is encrypted by each key, separately, and 
> that's what your multiple passwords decrypt.
> 
> See the tks-1 paper (iirc) referenced on the wiki for more info.

This is important as it means your disk encryption is basically as
strong as your "weaker key slot". e.g. a very bad password for one key
slot make all other passwords/keys inefficient.

Thanks, Karl, for the link.

Best,
Quentin

  reply	other threads:[~2011-09-19 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19 15:45 [dm-crypt] Questions about LUKS / LVM Robbie Smith
2011-09-19 16:00 ` Karl O. Pinc
2011-09-19 16:11   ` Quentin Lefebvre [this message]
2011-09-21 17:39     ` Yves-Alexis Perez

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=4E7769C7.5040805@laposte.net \
    --to=alto.spam@laposte.net \
    --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