From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] hard drive encryption
Date: Tue, 13 Mar 2012 17:49:40 +0100 [thread overview]
Message-ID: <4F5F7AA4.7030501@binarywings.net> (raw)
In-Reply-To: <CA+czFiBRUP2Er3+oVHFYPrMBEwDT7mv6H=ur1NE15AcY46BUpA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2777 bytes --]
Am 13.03.2012 17:26, schrieb Michael Mol:
> On Tue, Mar 13, 2012 at 12:11 PM, Florian Philipp <lists@binarywings.net> wrote:
>> Am 13.03.2012 12:55, schrieb Valmor de Almeida:
>>> On 03/11/2012 02:29 PM, Florian Philipp wrote:
>>>> Am 11.03.2012 16:38, schrieb Valmor de Almeida:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I have not looked at encryption before and find myself in a situation
>>>>> that I have to encrypt my hard drive. I keep /, /boot, and swap outside
>>>>> LVM, everything else is under LVM. I think all I need to do is to
>>>>> encrypt /home which is under LVM. I use reiserfs.
>>>>>
>>>>> I would appreciate suggestion and pointers on what it is practical and
>>>>> simple in order to accomplish this task with a minimum of downtime.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --
>>>>> Valmor
>>>>>
>>>>
>>>>
>>>> Is it acceptable for you to have a commandline prompt for the password
>>>> when booting? In that case you can use LUKS with the /etc/init.d/dmcrypt
>>>
>>> I think so.
>>>
>>>> init script. /etc/conf.d/dmcrypt should contain some examples. As you
>>>> want to encrypt an LVM volume, the lvm init script needs to be started
>>>> before this. As I see it, there is no strict dependency between those
>>>> two scripts. You can add this by adding this line to /etc/rc.conf:
>>>> rc_dmcrypt_after="lvm"
>>>>
>>>> For creating a LUKS-encrypted volume, look at
>>>> http://en.gentoo-wiki.com/wiki/DM-Crypt
>>>
>>> Currently looking at this.
>>>
>>>>
>>>> You won't need most of what is written there; just section 9,
>>>> "Administering LUKS" and the kernel config in section 2, "Assumptions".
>>>>
>>>> Concerning downtime, I'm not aware of any solution that avoids copying
>>>> the data over to the new volume. If downtime is absolutely critical, ask
>>>> and we can work something out that minimizes the time.
>>>>
>>>> Regards,
>>>> Florian Philipp
>>>>
>>>
>>> Since I am planning to encrypt only home/ under LVM control, what kind
>>> of overhead should I expect?
>>>
>>> Thanks,
>>>
>>
>> What do you mean with overhead? CPU utilization? In that case the
>> overhead is minimal, especially when you run a 64-bit kernel with the
>> optimized AES kernel module.
>
> Rough guess: Latency. With encryption, you can't DMA disk data
> directly into a process's address space, because you need the decrypt
> hop.
>
Good call. Wouldn't have thought of that.
> Try running bonnie++ on encrypted vs non-encrypted volumes. (Or not; I
> doubt you have the time and materials to do a good, meaningful set of
> time trials)
>
Yeah, that sounds like something for which you need a very dull winter
day. Besides, I've already lost a poorly cooled HDD on a benchmark.
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-03-13 16:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 15:38 [gentoo-user] hard drive encryption Valmor de Almeida
2012-03-11 18:29 ` Florian Philipp
2012-03-13 11:55 ` Valmor de Almeida
2012-03-13 16:11 ` Florian Philipp
2012-03-13 16:26 ` Michael Mol
2012-03-13 16:49 ` Florian Philipp [this message]
2012-03-13 16:54 ` Neil Bothwick
2012-03-13 16:54 ` Michael Mol
2012-03-13 17:45 ` Frank Steinmetzger
2012-03-13 18:06 ` Florian Philipp
2012-03-13 18:18 ` Michael Mol
2012-03-13 18:58 ` Florian Philipp
2012-03-13 19:13 ` Michael Mol
2012-03-13 19:30 ` Florian Philipp
2012-03-13 19:42 ` Michael Mol
2012-03-13 19:18 ` Florian Philipp
2012-03-13 21:05 ` Frank Steinmetzger
2012-03-13 19:07 ` Stroller
2012-03-13 19:38 ` Michael Mol
2012-03-13 20:15 ` Florian Philipp
2012-03-13 20:22 ` Florian Philipp
2012-03-13 20:02 ` Florian Philipp
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=4F5F7AA4.7030501@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.org \
/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