As a follow-up to yesterday’s post, here is the “Debian way” to do multiple LUKS-encrypted partitions on a system. In my case, I wanted to add a second drive, a backup storage drive, to my router. LUKS allows for multiple passwords or keyfiles to unlock a partition, which can be used to automate mounting. First, create a LUKS partition as normal (/dev/sdb1 assumed here):

# cryptsetup --verbose --cipher "aes-cbc-essiv:sha256" --key-size 256 --verify-passphrase luksFormat /dev/sdb1

We’ll need the key size, which I’m specifying in this case (256 bits), but if you’re using an existing LUKS partition, run this command and look for “MK bits”:

# cryptsetup luksDump /dev/sdb1

256 bits is 32 bytes, so we will need a 32-byte keyfile.

# dd if=/dev/random of=/etc/keys/sdb1_key bs=1 count=32

(Update, 2012-11-02: Previously that above line said “bs=32 count=1”. However, it appears if the RNG does not have enough entropy, dd will not wait around, and will instead just output the bytes it has. “bs=1 count=32” will force dd to block until it has all 32 bytes.)

Now add the keyfile to the partition. This can be done while the partition is loaded, mounted and in use. This command will ask you for one of your existing passphrases on the partition to gain access. Once you supply the phassphrase, the keyfile will be added to an open slot.

# cryptsetup luksAddKey /dev/sdb1 /etc/keys/sdb1_key

From this point, you can now unlock the partition using your existing passphrase, or you can specify the keyfile:

# cryptsetup --key-file /etc/keys/sdb1_key luksOpen /dev/sdb1 sdb1_crypt

Now for the Debian-specific part. If you would like this partition to be used upon bootup, add a line to /etc/crypttab:

sdb1_crypt /dev/sdb1 /etc/keys/sdb1_key luks

And then add a line to /etc/fstab:

/dev/mapper/sdb1_crypt  /opt/bigdrive   ext3    defaults                0       0

Debian (through /etc/init.d/cryptdisks) will take care of the luksOpen for you, and at that point /dev/mapper/sdb1_crypt is mounted as usual.

Safeguard this keyfile! There is no difference between the keyfile and a passphrase. Either will allow full access to the encrypted partition.

You could actually create a LUKS partition that is only keyfile-based, but you are out of luck if you lose the keyfile. In my case, I’m encrypting the backup drive, and storing the key on the backup server. If the backup server itself were to fail, I’d need a passphrase fallback to mount the backup drive to recover the backup server.