From: Robbie Smith <zoqaeski@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Questions about LUKS / LVM
Date: Tue, 20 Sep 2011 01:45:52 +1000 [thread overview]
Message-ID: <1316447158.7965.12.camel@zarniwoop> (raw)
Hello everyone
I'm contemplating setting up my new laptop to make use of LUKS + LVM
when I install Arch Linux on it, but I've got a few questions.
How much of a load on the system would LUKS + LVM be? Is it likely to
result in a noticeable drop in performance? 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?
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?
I'd just like to get as much information as possible before I set this
up, as I'm still not entirely sure if full-disk encryption is worth the
effort for a personal laptop.
Cheers if you can advise
Robbie
next reply other threads:[~2011-09-19 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 15:45 Robbie Smith [this message]
2011-09-19 16:00 ` [dm-crypt] Questions about LUKS / LVM Karl O. Pinc
2011-09-19 16:11 ` Quentin Lefebvre
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=1316447158.7965.12.camel@zarniwoop \
--to=zoqaeski@gmail.com \
--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