+ * 2.1 LUKS Container Setup mini-HOWTO
+
+ This item tries to give you a very brief list of all the steps you
+ should go though when creating a new LUKS encrypted container, i.e.
+ encrypted disk, partition or loop-file.
+
+ 01) All data will be lost, if there is data on the target, make a
+ backup.
+
+ 02) Make very sure you have the right target disk, partition or
+ loop-file.
+
+ 03) If the target was in use previously, it is a good idea to
+ wipe it before creating the LUKS container, in order to remove any
+ trace of old file systems, etc. For example, some users have
+ managed to run e2fsck on a partition containing a LUKS container,
+ possibly because of residual ext2 superblocks from an earlier use.
+ This can do arbitrary damage up to complete and permanent loss of
+ all data in the LUKS container.
+
+ To wipe, use something like
+
+ cat /dev/zero > target
+
+ This can take a while. To get a progress indicator, you can use
+ the tool dd_rescue (->google) instead or use my stream meter "wcs"
+ (source here: http://www.tansi.org/tools/index.html) in the
+ following fashion:
+
+ cat /dev/zero | wcs > target
+
+ Be very sure you have the right target, all data will be lost!
+
+ Note that automatic wiping is on the TODO list for cryptsetup, so
+ at some time in the future this will become unnecessary.
+
+ 04) Create the LUKS container:
+ cryptsetup luksFormat target
+
+ Just follow the on-screen instructions.
+
+ 05) Map the container. Here it will be mapped to /dev/mapper/c1:
+ cryptsetup luksOpen target c1
+
+ 06) (Optionally) wipe the container
+ cat /dev/zero > /dev/mapper/c1
+
+ Note that this creates a small information leak, as an attacker can
+ determine whether a 512 byte block is zero if the attacker has
+ access to the encrypted container multiple times. Typically a
+ competent attacker that has access multiple times can install a
+ passphrase sniffer anyways, so this leakage is not very
+ significant. For getting a progress indicator, see step 03.
+
+ Note that at some time in the future, cryptsetup will do this for
+ you, but currently it is a TODO list item.
+
+ 07) Create a file system in the mapped container, for example an
+ ext3 file system (any other file system is possible):
+
+ mke2fs -j /dev/mapper/c1
+
+ 08) Mount your encrypted file system, here on /mnt:
+ mount /dev/mapper/c1 /mnt
+
+ Done. You can now use the encrypted file system to store data. Be
+ sure to read though the rest of the FAQ, these are just the very
+ basics. In particular, there are a number of mistakes that are
+ easy to make, but will compromise your security.
+
+
+ * 2.2 What is the difference between "plain" and LUKS format?