This post will (try to) explain how to set up a working system of hard drive encryption on a Debian system, in this case sidux. I’m going to outline the specific course of action I took to set up my own laptop, but will try to provide generic enough instructions alongside that to help the reader adapt it for themselves. Please excuse the wild tense changing and poor overall writing style, I’m not that good at this stuff.
This post is not aimed at the novice Linux user. I’m not going to hold your hand, so be comfortable with the command line and competent enough to get your system back if you screw up along the way. Also, do not skip the backup step! Finally, this is (obviously) not a wholly original and independent work, I owe a great deal to the sources I’ve listed at the bottom. Enjoy!
I run Linux on my laptop and I want to encrypt the important parts of my hard drive because there is a lot of my personal life on there. Most specifically I’m interested in my passwords, many of which I store in firefox Iceweasel for convenience, and my financial data which is in the form of KMyMoney files and pdf receipts.
Here’s the layout of my disk, and yes I know I have outrageous sizes on some of these partitions, I just like to have breathing room. Please see  for a good guide to partitioning.
What we need to encrypt on there are: /home, /tmp, /data and /swap. I’ll be treating the /windows and the /winshare as dirty and never let anything important touch those partitions, I rarely boot into XP for anything but school work anyway.
You’ll need a very few pieces of software, and possibly a piece of hardware. For the software side you just need “cryptsetup” and possibly a partitioning tool if you want to change your layout. You’ll also be needing some spare hard drive space to hold your existing data if you have any. I used an 80 GB external drive I had on hand.
I’m using an existing system as my base, so I have to copy off my /home and /data partitions. Once we are backed up, it’s important to write down somewhere the /dev names of the file system. I made a little table, like the one above, by using gparted.
Now I’m going to go down to run level 3. This is just to minimize noise on the system. We need to unmount /home, /data and /tmp. When unmounting file systems, you might get something like the following error:
[email protected]:/home/jmhobbs# umount /tmp umount: /tmp: device is busy umount: /tmp: device is busy [email protected]:/home/jmhobbs#
This just tells us there is an open file descriptor on /tmp, we can see who has it with:
[email protected]:/home/jmhobbs# lsof | grep /tmp COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME atievents 3037 root 4r DIR 254,2 4096 29249 /tmp/.X11-unix kdeinit 5418 jmhobbs 8u unix 0xf31fc000 11568 /tmp/ksocket-jmhobbs/kdeinit- gconfd-2 6127 jmhobbs 11wW REG 254,2 625 102371 /tmp/gconfd-jmhobbs/lock/0t1201112611ut204480u1000p6127r1358695165k3219666472 (deleted) konqueror 6627 jmhobbs 12u REG 254,2 1270 58498 /tmp/kde-jmhobbs/konqueror-crash-y2tzca.log [email protected]:/home/jmhobbs#
Now in the above example it is obvious that I did not go down to run level 3, X11 and kde are still running. So just weed out the open files and then unmount them when there are none left.
This is where that /dev table you made earlier (you did make it right?) comes in handy. Be sure that you are backed up, because this is the point of no return. Setting up an encrypted partition is dead simple. As root you’ll want to run:
cryptsetup --verbose --verify-passphrase luksFormat /dev/sda9
Now we need to open and format that, so we use cryptsetup to open it:
cryptsetup luksOpen /dev/sda9 chome
This is going to create a mapper device called “chome” in /dev/mapper/chome. You don’t need to call it chome, I just do it to keep track of whats what.
Now to format it we need to do:
mkfs.ext3 -j -m 1 -O dir_index,filetype,sparse_super /dev/mapper/chome
The file system really doesn’t matter, you can use ext2, reiserfs, whatever your heart desires. Once you’ve done that, you’ll want to close it again.
cryptsetup luksClose chome
We need to repeat that process for /data, but since it’s essentially the same procedure I’m not going to run through it here.
The /tmp partition is a different story. You’ve got an existing file system on there that we need to blow away. The first way that came into my head was to use dd to copy zeros over it, like so:
dd if=/dev/zero of=/dev/sda7
That’ll probably take a while and not report in. You can force it to give you a status by stopping it, sending it a USR1 signal then restarting it. Not really a big deal though, I just waited it out.
It also might be wise to increase the block size on that, and you might not have to do the whole thing either. Again, refer to the man pages  if it concerns you.
Set Up crypttab And fstab
We now need to update our fstab and the crypt equivalent, crypttab. This is going to vary for everyone, but there are a few key things to note. Let’s look at crypttab first. Here’s mine, and I’ll walk you through it.
So the major things here are the target, which is what the device will be called in /dev/mapper. I picked the easy to associate: chome,cdata, cswap, and ctmp. Next is the source device, which are the partitions we messed with earlier. The key file is set to /dev/random on cswap and ctmp because those are going to be one time file systems, and the key should just be random garbage.
Finally we get to options. chome and cdata have “none” in there. This is just saying “prompt us for the password”. You could put the password in there and it would happily take care of it for you, but that seems like a stupid thing to do to me. The “luks” just tells it to use the luks extensions. cswap and ctmp both use special options. The swap and tmp options basically say “reformat this then encrypt it”. They are reformatted on boot to linux-swap and ext2 file systems, respectively. For more information check out the, you guessed it, man page .
Now that we’ve got the crypttab set up we need to modify out fstab. Again, I’ll show you the relevant parts of mine, and walk you through. It’s pretty simple though.
# /etc/fstab - static information about the filesystems - fstab(5) #
# automatically added, WDC_WD2500BEVS-0-WD-WXC607403544-part2, /dev/sda2 UUID=60a14eae-a8c7-4ecb-a222-79a0e97fd73e / ext3 defaults,noatime,errors=remount-ro 0 1 # automatically added, WDC_WD2500BEVS-0-WD-WXC607403544-part7, /dev/sda7 #UUID=0da43c8e-2a64-4f45-b967-91504b4aa167 /tmp ext3 defaults,noatime 0 2 /dev/mapper/ctmp /tmp ext2 defaults,noatime 0 0 # automatically added, WDC_WD2500BEVS-0-WD-WXC607403544-part9, /dev/sda9 #UUID=3ee7225e-f04a-4d96-b28d-e867ed38a73c /home ext3 defaults,noatime 0 2 /dev/mapper/chome /home ext3 defaults,noatime 0 2 # automatically added, WDC_WD2500BEVS-0-WD-WXC607403544-part4, /dev/sda4, LABEL=\x2fdata #UUID=e3e9105b-1820-4edc-a660-7d569bc61900 /data ext3 auto,users,exec,noatime 0 2 /dev/mapper/cdata /data ext3 defaults,noatime 0 2 # automatically added, WDC_WD2500BEVS-0-WD-WXC607403544-part6, /dev/sda6 #UUID=21ac314b-704b-4675-bf5e-769745b46f7a none swap sw 0 0 /dev/mapper/cswap none swap sw 0 0
Okay, so, the basic idea is that we find the old /tmp, /home, /data and swap entries, and replace them with the mapped ones. One important item here is that you’ll want to set that last digit to a 0 on /tmp. This is what says “Hey, fsck me!” at boot time, and we don’t want to bother with a checking a brand new file system, right?
cryptdisks And cryptdisks-early
These two are the init scripts for starting up your disks. They should be in /etc/init.d, which on my system just lead to /lib/cryptsetup/cryptdisks.functions. I tried using bum to add them, but I wasn’t getting them to run before the mounting took place. I poked around on the sidux forums and found a post  (in German) that had another way of adding them. I don’t know if this is a Debian issue or not, but the following worked for me, as root.
update-rc.d -f cryptdisks-early remove update-rc.d -f cryptdisks remove update-rc.d cryptdisks-early start 26 S . start 59 0 6 . update-rc.d cryptdisks start 28 S . start 48 0 6 .
Now you should be able to just reboot and be good to go. I’m not 100% on this guide as I made it after the fact, so I may have spaced off some small things. If I did, they should be very, very minor and shouldn’t cause any problems. Please do leave comments if you have an issue, I’d like to correct any errors I may have made. There are some additional sources below, please read up if you have the time. Good luck!