At this point, encryption is an issue of social responsibility. It is important to establish a norm that data should not live or travel in plaintext without an affirmative reason, especially if you have nothing to hide, because it provides cover to the people who do. Besides the normative aspect, if you intend on doing any international travel, have any interesting friends, or do any interesting or profitable work on your machine, you owe it to yourself to secure your environment.
Ubuntu makes the single-disk encryption scenario relatively easy, but it doesn’t allow a lot of customization at install time, and has no GUI for extending encryption to multiple disks. Fortunately it’s only a bit more CLI work to set it up to work transparently with multiple disks, so you only need to enter the one passphrase. I’ve tested this in a VM with the latest Ubuntu 14.04 beta, but it should work for other versions of Ubuntu, or any distro with support for cryptsetup.
The defaulted Ubuntu “encrypt my whole hard drive” installer layers like so:
- The physical disk
- An extended physical partition
- A LUKS wrapper
- A LVM physical volume
- Two LVM logical volumes: one for swap, and one EXT4 filesystem for your root directory.
Whew! This is probably fine for your system drive, if a little complex; it’s nice being able to use LVM to resize your swap partition if your needs change dramatically, and if your system drive is a different size / speed than those in your storage array (eg, a 32GB SSD vs. an array of 4TB spinny disks) it wouldn’t make sense to have it as part of the same filesystem anyway. We’ll accept that default for our root partition and swap, and focus on our secondary data drives.
We’ll assume your main system has been installed successfully on /dev/sda , and we have 2 other disks /dev/sdb and /dev/sdc that we want to set up as an encrypted, Btrfs-managed mirror.
First, let’s blow away the existing disks, and create some fresh partitions. You can do this graphically or through any partition editor. The key thing is to end up with one unformatted partition on each disk; /dev/sdb1 and /dev/sdc1 respectively.
# You’ll need to be superuser for all of this sudo -i # For these commands, select "o" to zero the partition table, # "n" to create a new partition (follow the defaults for a single primary # partition that fills all space), then "w" to write to disk. fdisk /dev/sdb fdisk /dev/sdc
We’re going to use a keyfile so we only have to enter the passphrase that unlocks our root partition. Let’s generate one.
# 512 bit / 64 byte keyfile dd if=/dev/random of=/etc/keyfile bs=1 count=64
Create a couple of LUKS wrappers inside those partitions, using the keyfile we just generated
cryptsetup --key-file /etc/keyfile -v luksFormat /dev/sdb1 cryptsetup --key-file /etc/keyfile -v luksFormat /dev/sdc1
Now we load the encrypted mapping, to /dev/mapper/enc1 and /dev/mapper/enc2 respectively, again using the keyfile. We write plaintext into the mapper, and it comes out encrypted on the raw device.
cryptsetup --key-file /etc/keyfile luksOpen /dev/sdb1 enc1 cryptsetup --key-file /etc/keyfile luksOpen /dev/sdc1 enc2
Now we make a choice. Btrfs has its own LVM-esque capabilities, so rather than layer in more complexity by using logical volumes, we use Btrfs directly inside the LUKS wrapper.
# Btrfs isn’t installed by default apt-get install btrfs-tools # A label makes management slightly easier. mkfs.btrfs -L vol1 -m raid1 -d raid1 /dev/mapper/enc1 /dev/mapper/enc2 # The final mount point mkdir /mnt/enc # We can mount any of the component devices manually, and have access to the full array mount /dev/mapper/enc1 /mnt/enc
OK, let’s modify our fstab and our crypttab so our system knows to decrypt and mount these drives. This should be added to your crypttab (optionally replacing the devices with their UUIDs, which you can get via “sudo blkid”):
# Optionally add "discard" to options to support TRIM on SSDs enc1 /dev/sdb1 /etc/keyfile luks enc2 /dev/sdc1 /etc/keyfile luks
And this should be added to your fstab (again optionally using UUID, or the label of the array):
/dev/mapper/enc1 /mnt/enc btrfs defaults 0 2 # Optionally, using label: # LABEL=vol1 /mnt/enc btrfs defaults 0 2
Now, when you boot, you will be asked for your root passphrase first. The keyfile will be decrypted, and used to decrypt your Btrfs component drives. They will then be mounted, and your data will be secure.
I’m told that some people’s setups required a bit more massaging to get up and running with automount. Their fix involved adding a “device” parameter to the fstab, something like the following:
/dev/mapper/enc1 /mnt/enc btrfs device=/dev/mapper/enc1,device=/dev/mapper/enc2 0 2