After mounting that filesystem and creating a trivial file I unmount it again and locked the encrypted volume. I name this encrypted volume myencryptedstuff and create an ext3 filesystem on it. To get started, as you’ll see in the code below, I formatted /dev/sdc1, destroying all of the data on that partition in order to make a new encrypted volume. Although I am using a partition to contain the encrypted filesystem, you can also use a single file mounted through a loopback device if you do not have a spare partition. I used a LUKS encrypted volume as an example of pam_mount usage. Mount.crypt -o cipher=aes '%(ifnempty='-o' OPTIONS)' %(OPTIONS) The only change needed (shown below) was that I had to tell mount.crypt which cipher was used: I installed version 0.48 from the Fedora repositories on a 64-bit Fedora 9 machine, but I also tested version 1.2, and it worked exactly the same way. Ubuntu Hardy packages it as libpam-mount. The distribution repositories for Fedora 9 include pam_mount and it is available as a 1-Click for openSUSE 11. Last month the project made a major version jump from 0.49 to 1.2, so don’t be too alarmed if your distribution is still offering older code. We’ve written about other alternatives for providing encrypted filesystems, such as EncFS and Loop-AES, dm-crypt, and Cryptmount, but pam_mount makes the whole process seamless. And pam_mount can mount any filesystem, not just encrypted filesystems, so you can use it, for example, with an NFS share that you are interested in but which you might not like to leave mounted when you are not logged in. Using this method, you can easily share a laptop and have only a single user’s home directory unlocked and mounted when he logs in. The same password used to log in is used as the key to unlock the encrypted filesystem, so you only need to type it once. The pam_mount project lets you unlock an encrypted filesystem automatically when you log in.

Linux mount encrypted dmg