Preserving privacy by encrypting block devices
Rules of Thumb
The risk of forgetting a passphrase can lead to really bad habits, such as using very simple passphrases or writing them down. With this in mind, I have a couple of rules of thumb.
- If you need to encrypt a file or a just a few files, use something like 7-Zip, which compresses the files and encrypts the archive as well. The simplicity of this method not only empowers the user to make the decision about what to encrypt but also puts the responsibility of encryption and decryption and remembering the passphrase on the user.
- If you need to encrypt directory trees (e.g., if someone is working on a project or data storage is structured), then you have a couple of options. The first, EncFS , allows the user to control what they want to encrypt and where it should be mounted. Again, this puts the management of passphrases and encryption in the hands of the user, with all the benefits and disadvantages. The second option, eCryptfs , can encrypt a directory structure, but that is under the control of the administrator. Creating an encrypted directory for each user to use to encrypt their data is fairly easy. Although the user has the responsibility of copying the data to this folder to encrypt it, remembering the passphrase again falls to the administrator.
If the situation is such that all, or virtually all, data needs to be encrypted, then using a block device encryption tool such as DMCrypt or TrueCrypt works very well. Alternatively, you could use an SED, but the effects on users and administrators is almost the same for either approach. In the case of software encryption such as DMCrypt or TrueCrypt, it might require an extra command or a different command to mount and unmount the block device. In the case of SEDs, the administrator just has to remember the passphrase when the disk is accessed (usually before the system boots). After that, all the admin commands are the same.
I wish you good luck in your encryption mission; if you choose to accept it, I have one last word of advice: hAS(*ja[p18a8@asj.
- DMCrypt: http://en.wikipedia.org/wiki/Dm-crypt
- Crypto API: http://en.wikipedia.org/wiki/Crypto_API_%28Linux%29
- LUKS and cryptsetup: http://code.google.com/p/cryptsetup/
- Passphrase, Wikipedia (CC BY-SA 3..0): http://en.wikipedia.org/wiki/Passphrase
- TrueCrypt: http://www.truecrypt.org/
- TrueCrypt licensing: http://en.wikipedia.org/wiki/TrueCrypt#Licensing_and_Open_Source_status
- Open Source Initiative: http://opensource.org/
- Keyfiles: http://www.truecrypt.org/docs/keyfiles
- EncFS: http://www.arg0.net/encfs
- eCryptfs: http://ecryptfs.org/
Buy this article as PDF
New flaw in an old encryption scheme leaves the experts scrambling to disable SSL 3
Lennart Poettering wants to change the way Linux developers talk to each other.
Enterprise giant frees itself from ink and home PCs (and visa versa).
Mozilla’s product think tank sinks silently into history.
TODO group will focus on open source tools in large-scale environments.
New tool will look like GParted but support a wider range of storage technologies.
New public key pinning feature will help prevent man-in-the-middle attacks.
Carnegie Mellon researchers say 3 million pages could fall down the phishing hole in the next year.
The US government rolls new best-practice rules for protecting SSH.