Since Dropbox fucked us all over by dropping support for filesystems that aren’t ext4, all the cool things you used to be able to do like encrypting your home folder dead easily with ecryptfs, snapshots with btrfs, LVM etc. are all stuffed. Now the OS must only see a pure ext4 file system, otherwise the Dropbox client will detect it and refuse to synchronise.
There is a solution using loopback mounting to create an ext4 specific to Dropbox; that’s fine but it means you are setting aside a certain amount of space to dedicate to Dropbox, and if your Dropbox gets bigger than that you’re going to have a pain resizing it. Instead I wanted to encrypt the root partition as well, and I want the simplicity and flexibility of one home directory not carved up into special partitions for Dropbox. So this is how I used LUKS to encrypt all my partitions, but without putting LVM in the middle.
This was tested with Mint 19. Should work on Ubuntu and probably Debian.
- Have some experience with Linux so don’t need total hand holding
- Don’t want to run a script to configure all this as you want to see/learn what’s going on
- Aren’t in super-paranoid security mode
- Want to dual boot
- Not bothered about hibernation
- Happy with a swap file instead of a swap partition (default in recent ubuntus)
- Boot new laptop into Windows
- Perform all Windows updates
- Perform all manufacturer driver updates, especially BIOS
- Create a recovery drive (allows us to delete the recovery partition and get that space back)
- Run Manage BitLocker and switch off BitLocker (needed so that the Linux installer can safely resize it).
- Run Disk management and make sure you understand what partitions exist and what they are all for.
- Use the BIOS to disable Secure Boot. You can switch it back on later and it’s just going to cause you a problem in the short term.
Partition preparation and OS installation
- Boot from Linux live USB (in my case Mint 19)
- Confirm that you have booted in UEFI mode (and not legacy mode). Open a terminal and run:
It should return a list of bootable devices and the current boot order. If it returns an error about EFI variables not being supported, then you are booted in legacy mode and need to fix that first.
- Run gparted (you can’t do this using the partitioning tool built in to the installer, because the moment it has finished creating the partitions it will then try to start installing to them. You need to insert the encryption set up in between these steps, so we’ll do it before even running the installer).
- Delete recovery partitions you have decided you don’t want; you won’t need these if you made the recovery drive above. The partition that was called WINRETOOLS in Windows (about 1Gb) can go.
- Resize the main Windows partition as small as you dare to without making it unusable. These days I’d recommend at least 90Gb if it’s a secondary OS. Mine’s 55Gb after updates are all applied and before I’ve installed any apps or put any data on it. Yikes.
- In the free space you now have, create your desired Linux partitions as ext4. Make sure you set labels and partitions names. You WILL need a separate /boot partition, and GRUB has to be able to find the kernel image in an unencrypted form in order to then access then other encrypted partitions.Here’s my choice for a 512Gb drive:
|New size (Mb)
||File system type
||File system label
I separate root and home so that I can reduce the reserved space on /home to 0 whilst maintaining it at 5% on /; I can fill my home drive to the tippy-top without destabilising the system.
50Gb might seem a lot for the root partition but Linux distributions are getting as big as Windows. I’ve been running a 25Gb root partition for the last few years and I’m getting bored with having to keep tidying it up so that I’ve got room to download updates.
- Open a terminal, and enter
to switch to a root prompt.
- Next enter
list all your new partitions, and note the Device names for them.
- Now we’ll encrypt the non-boot partitions. You’ll need to invent some secure passphrases for them. For the root partition you’ll be entering this every time you turn the computer on, so make this secure but typeable. For the others they’ll just be emergency backups so you can make them a bit weirder if you like. To encrypt:
once for each partition that is NOT /boot. So for me:
cryptsetup luksFormat /dev/sda5
cryptsetup luksFormat /dev/sda6
You’ll get prompted for your chosen passphrase for each. Beware keyboard layouts; the live USB may have chosen a US keyboard layout, so if your chosen passphrase contains any characters that would be different on a US keyboard then you will not be setting the password to what you think you are. Remember that in future if something has gone wrong during boot and you are dropped to a root prompt or even being prompted by the kernel for the passphrase for the root paritition, you may not have the luxury of selecting they keyboard layout. So probably choose a passphrase with just letters and numbers. Or even just letters: making it longer is much better than using a bigger character set.
- Now we’ll unlock them so that the installer can see them and use them as partitions. To unlock:
once for each partition that is NOT /boot. So for me:
cryptsetup open /dev/sda5 cryptroot
cryptsetup open /dev/sda6 crypthome
This creates the two pseudo-partitions /dev/mapper/cryptroot and /dev/mapper/crypthome which the installer can treat as unencrypted partitions and write to normally.
- Now we’ll format them:
mkfs.ext4 -L /dev/mapper/
once for each partition that is NOT /boot. So for me:
mkfs.ext4 -L ROOT /dev/mapper/cryptroot
mkfs.ext4 -L HOME /dev/mapper/crypthome
- All is now ready for OS installation. You’ll need at some point to override the installer’s partitioning scheme, choosing Custom or Something else or whatever option allows you to specify what partitions are used and where. Then set the unencrypted boot partition to be mounted at /boot, and the new /dev/mapper/cryptroot and other partitions to have their appropriate mount points. You don’t need to format them as they are new. Make sure the boot loader is configured to be installed on /dev/sda. Don’t select any options for encryption in the installer – you’ve already done it. Once installation is complete, don’t reboot. There’s more to do yet.
Post installation fiddling
From this point onwards I’m going to assume that you are capable of substituting your device names, map names, labels etc. if you have used different values to me, and I’ll just show you what I used.
- Now we’ll mount the newly-populated partitions to do some fiddling. Run
mkdir -p /mnt/root/boot/efi
mount /dev/mapper/cryptroot /mnt/root
mount /dev/mapper/crypthome /mnt/root/home
mount /dev/sda4 /mnt/root/boot
mount /dev/sda1 /mnt/root/boot/efi
mount --bind /dev /mnt/root/dev
mount --bind /proc /mnt/root/proc
mount --bind /sys /mnt/root/sys
/dev/sda4 is my boot partition, and /dev/sda1 is my EFI partition (created by Windows). Consult your
fdisk -l output from earlier to see which ones yours are.
- Now we’ll grab the UUIDs of the encrypted partitions we made:
lsblk --paths --output=NAME,UUID | grep -v mapper
You’ll need the UUIDs of your root and home and any other partitions.
- Now we’ll tell the OS to unlock our encrypted drives while it is booting. Add lines like this to the new file /mnt/root/etc/crypttab:
cryptroot UUID=756125d1-7845-ab56-cd56-780a-4a45cb56d4cb none luks,discard,noearly
crypthome UUID=aa54bc47-2356-554d-d5c6-41ac-4a45cb5456a8 none luks,discard,noearly
Note that these are the UUIDs of /dev/sda5 etc., not the UUIDs of /dev/mapper/cryptroot etc
- Improve the security on this file for when we later embed passphrases into it:
chmod -rw /mnt/root/etc/crypttab
- Set these values in /mnt/root/etc/default/grub:
Again this is the UUID of the underlying root device such as /dev/sda5.
- Now re-configure the Grub menu entries:
- That’s it. You can reboot. Your OS should now boot. You’ll get prompted twice to enter the passwords for your encrypted partition, once for your root partition and once for your home (and more for any others you made). In the next section we’ll eliminate some of those. For now, give yourself a pat on the back for getting this far.
All well and good so far, but having to unlock each partition separately is a bit of a pain in the bum. Time to rectify that. Each partition can have up to eight passphrases associated with it, and those passphrases can be files as well as typed-in passphrases. So next we’ll let the root partition auto-mount the /home partition without us having to type in the passphrase.
- Open a terminal on your new installation. Type:
dd if=/dev/urandom of=/etc/crypt.home count=1 bs=512
cryptsetup luksAddKey /dev/sda6 /etc/crypt.home
This puts 512 bytes of randomness into the file /etc/crypt.home, and stores it as a second password for the /home partition.
- Next we open the file /etc/crypttab. Against the home partition where we had none (which causes it to prompt you for a passphrase), we will now specify a keyfile instead:
crypthome UUID=aa54bc47-2356-554d-d5c6-41ac-4a45cb5456a8 /etc/crypt.home luks,discard,noearly
- Reboot. Now you should only be prompted for the password for your root partition, and home should auto-mount.
Should something ever go wrong, the password you originally set for the home partition is still valid, so you can use that as a recovery password for getting in to it. Store it safely.
By now you’re thinking “Why don’t I do this for the root partition too?”. You’d have to store it somewhere else that wasn’t the (not-yet-unlocked) root partition. That couldn’t be the /boot partition, as that isn’t encrypted (the way we’ve done it), so you’d be storing the keys to the kingdom in the clear for your laptop thief to recover. Instead, here’s a nicer way – store it on a USB drive. If the drive is plugged in, use it to open the root partition automatically. If it isn’t prompt for a password. If you leave this drive plugged in to a USB hub at home, then whenever you are at home it will be there and unlock automatically, but if you take the laptop elsewhere the drive won’t be attached and the passphrase will be requested. Automatic security the moment you leave the house!
- Get a sacrificable USB drive. You will erase all its content, and probably never use it for anything else again. I would recommend one with a clearly visible light, and without any fancy retraction mechanisms. You don’t want there to be iffiness about whether it’s plugged in or not. Smaller is better, it really only needs to be a few Mb in size.
- plug in the drive and open a terminal again:
Look at the end of the output from dmesg to see what device name your drive has been given. If you only have one internal drive and this is the only stick plugged in it will probably be sdb, but it’s best to check.
- Destroy the contents of the stick by filling it with random data:
dd if=/dev/urandom of=/dev/sdb bs=1
The bigger the stick the longer this will take.
- Extract a key from the randomness written to the drive and add it as a passphrase for the root partition:
dd if=/dev/sdb of=/etc/crypt.root bs=1 count=512
cryptsetup luksAddKey /dev/sda5 /etc/crypt.root
- Note down the path to the USB drive:
If it’s not obvious which one it is, you can pull the stick out and ls again to see which entry has disappeared. Copy this into your clipboard.
- Create this file as _/usr/local/sbin/unlockusbkey.sh_:
# flag tracking key-file availability
# give the system time to settle and open the USB device
# check for the specific USB key
if [ -b $USBKEY ]; then
# if device exists then output the keyfile from the usb key
dd if=$USBKEY bs=1 count=512 | cat
if [ $OPENED -ne 0 ]; then
echo "FAILED to get USB key file ..." >&2
if [ -x /bin/plymouth ] && plymouth --ping; then
plymouth ask-for-password --prompt "Enter passphrase"
/lib/cryptsetup/askpass "Enter passphrase"
echo "Success loading key file. Moving on." >&2
- Modify the root partition entry of _/etc/crypttab_ to add the keyscript option on to the end:
cryptroot UUID=756125d1-7845-ab56-cd56-780a-4a45cb56d4cb none luks,discard,noearly,keyscript=/usr/local/sbin/unlockusbkey.sh_
- Finally, rebuild initramfs:
All done. Now if you boot with the stick in the root partition should be unlocked automatically, and if you boot without you’ll be promptd for its password. Enjoy!