Some days ago, @firstname.lastname@example.org convinced me on Mastodon to give BTRFS a try. That’s actually been a feature on my list for some time already, and now that I need to switch PCs at work I’m going for it. However, this post wouldn’t exist if everything went straight forward.. ;-)
I have a 1TB SSD that I want to encrypt. It should automatically get decrypted and mounted to certain places when I log in. pam_mount can do that for you, and I’ve already been using that a lot in different scenarios. However, with BTRFS it’s a bit different. With any other file systems you would create a partition on the hard drive, which is then LUKS encrypted. This has the drawback, that you need to decide on the partition’s size beforehand!
With BTRFS you can just encrypt the whole drive and use so-called subvolumes on top of it. Thus, you’re a bit more flexible by creating and adjusting quotas as required at any point in time (if at all…), but (or and!) the subvolumes are not visible unless the device is decrypted.
Let’s have a look into that and create the scenario.
I assume that the SSD is available as
Then we can create an encrypted container using LUKS:
You’re not sure which cipher or key-size to choose?
cryptsetup benchmark to see which settings perform best for you.
My CPU, for example, comes with hardware support for AES, thus the AES ciphers show a significantly higher throughput.
If you’re still feeling uncompfortable with that step, I recommend reading the sophisticated article at the
ArchLinux’ wiki on dm-crypt/Device encryption.
We can now open the encrypted device using
This will create a node in
/dev/mapper/mydrive, which represents the decrypted device.
Next, we’ll create a BTRFS on that device:
That’s indeed super fast, isn’t it!? I also couldn’t believe it.. ;-)
We can now mount the device, for example to
So far, the file system is completely empty.
But as it’s a BTRFS, we can create some subvolumes.
Let’s say, we want to create a volume for our
$HOME, and as we’re developing this website, we also want to create a volume called
So we have two subvolumes in that file system:
We could now mount them with
But we want the system to do it automatically for us, as we login.
So unmount everything and close the LUKS container:
PamMount can Decrypt and Mount Automatically
pam_mount already for ages! It is super convenient.
To get your home automatically decrypted and mounted, you would just need to add the following lines to your
Here, I am using UUIDs to identify the disks.
You can still use
/dev/sdb (or similar), but there is a chance, that the disks are recognised in a different sequence with the next boot (and
/dev/sdb may become
/dev/sdc or something…).
Plus, the UUID is invariant to the system – you can put the disk in any other machine and it will have the same UUID.
To find the UUID of your disk you can use blkid:
As said above, with BTRFS you’ll have your partitions (called subvolumes) right in the filesystem – invisible unless decrypted.
So, what is PAM doing?
It discovers the first entry in the
pam_mount.conf.xml configuration, which basically says
a1b20e2f-049c-...with some extra options to
PAM is also smart enough to understand that
a1b20e2f-049c-... is a LUKS encrypted device and it decrypts it using your login password.
This will then create a node in
/dev/mapper/_dev_sdb, representing the decrypted device.
And eventually, PAM mounts
So far so perfect.
But as soon as PAM discovers the second entry, it tries to do the same!
Again it detects a LUKS device and tries to decrypt that.
But unfortunately, there is already
Thus, opening the LUKS drive fails and you’ll find something like that in your
First it seems annoying that it doesn’t work out of the box, but at least it sounds reasonable that PAM cannot do what you what it to do..
… is quite easy, even though it took me a while to figure things out…
As soon as the first subvolume is mounted (and the device is decrypted and available through
/dev/mapper/_dev_sdb), we have direct access to the file system!
Thus, we do not neet to tell PAM to mount
/dev/disk/by-uuid/a1b20e2f-049c-..., but we can use
Or even better, we can use the file system’s UUID now, to become invariant to the
If you run
blkid with the device being decrypted you’ll find an entry like this:
You see, the new node
/dev/mapper/_dev_sdb also carries a UUID, actually representing the BTRFS :)
This UUID was by the way also reported by the
mkfs.btrfs call above.
What does that mean for our setup? When we first need a subvolume of an encrypted drive we need to use the UUID of the parent LUKS container. For every subsequent subvolume we can use the UUID of the internal FS.
Transferred to the above scenario, we’d create a
/etc/security/pam_mount.conf.xml like that:
Note the different UUIDs? Even though both mounts origin from the same FS :)
Actually, I wanted to have my home in a raid of two devices, but I don’t know how to tell
pam_mount to decrypt two devices to make BTRFS handle the raid..?
The only option seems to use mdadm to create the raid, but then BTRFS just sees a single device and, therefore, cannot do its extra raid magic…
If anyone has an idea on that issue you’ll have my ears :)
- administration (33) ,
- hardware (15) ,
- software (146) ,
- linuxunix (21) ,
- operatingsystem (14) ,
- howto (20) ,
- debian (24) ,
- university (42) ,
- security (28)
- btrfs (1) ,
- ssd (1) ,
- mastodon (1) ,
- pam (2) ,
- crypt (3) ,
- auth (2) ,
- config (14) ,
- debian (36) ,
- explained (37) ,
- security (30) ,
- university (39)