Speaking just for myself, I don't like to encrypt the system. It is more complicated to do and, should there be a problem where a recovery is needed, your problem is a lot more complicated if the system is encrypted. For the same reason, I don't put the system on a logical volume.
Also, I have had some truly unpleasant experiences doing version upgrades with encrypted systems; I have seen the initrd improperly built more often than not.
I do avoid data leaks by encrypting everything else (including swap) and I symlink specific locations in the / filesystem to locations on other volumes in order to keep the data private. On my workstation (which has a bunch of different volumes and is fully encrypted except for /) I have /tmp, /var/cache, /var/lib/mysql, /var/tmp, /var/spool/cron, and /var/www all symlinked to other encrypted volumes.
I also am very careful to keep backups of the MBR and the encrypted filesystem header for each physical disk and each encrypted partition. I keep these on the encrypted volumes, but there are multiple copies so that if any given encrypted volume is inaccessible due to damage or corruption, I can recover it by getting the copy of the keys from a backup on another volume. I do the backup and restores as follows:
- Code: Select all
sudo cryptsetup luksHeaderBackup --header-backup-file=sdf1 /dev/sdf1
To restore the crypto data to the drive, use the inverse command:
cryptsetup luksHeaderRestore --header-backup-file=sdf1 /dev/sdf1
All that said, if you must encrypt your systems, you could use one LVM if you wanted to, and just partition the logical volume. Probably safer to set up two logical volumes though.