1. General Questions
- * What is this?
+ * 1.1 What is this?
This is the FAQ (Frequently Asked Questions) for cryptsetup. It
covers Linux disk encryption with plain dm-crypt (one passphrase,
http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions
- * WARNINGS
+ * 1.2 WARNINGS
ATTENTION: If you are going to read just one thing, make it the
section on Backup and Data Recovery. By far the most questions on
backup is mandatory, see Section "6. Backup and Data Recovery" on
options for doing encrypted backup.
+ CLONING/IMAGING: If you clone or image a LUKS container, you make a
+ copy of the LUKS header and the master key will stay the same!
+ That means that if you distribute an image to several machines, the
+ same master key will be used on all of them, regardless of whether
+ you change the passphrases. Do NOT do this! If you do, a root-user
+ on any of the machines with a mapped (decrypted) container or a
+ passphrase on that machine can decrypt all other copies, breaking
+ security. See also Item 6.15.
+
DISTRIBUTION INSTALLERS: Some distribution installers offer to
create LUKS containers in a way that can be mistaken as activation
of an existing container. Creating a new LUKS container on top of
installers after a complete backup of all LUKS containers has been
made.
+ NO WARNING ON NON-INERACTIVE FORMAT: If you feed cryptsetup from
+ STDIN (e.g. via GnuPG) on LUKS format, it does not give you the
+ warning that you are about to format (and e.g. will lose any
+ pre-existing LUKS container on the target), as it assumes it is
+ used from a script. In this scenario, the responsibility for
+ warning the user and possibly checking for an existing LUKS header
+ is shifted to the script. This is a more general form of the
+ previous item.
+
LUKS PASSPHRASE IS NOT THE MASTER KEY: The LUKS passphrase is not
used in deriving the master key. It is used in decrypting a master
key that is randomly selected on header creation. This means that
http://en.wikipedia.org/wiki/ASCII
- * System Specific warnings
+ * 1.3 System Specific warnings
- Ubuntu as of 4/2011: It seems the installer offers to create
LUKS partitions in a way that several people mistook for an offer
http://launchpad.net/bugs/420080
- * Who wrote this?
+ * 1.4 Who wrote this?
Current FAQ maintainer is Arno Wagner <arno@wagner.name>. Other
contributors are listed at the end. If you want to contribute, send
least problems.
- * Where is the project website?
+ * 1.5 Where is the project website?
There is the project website at http://code.google.com/p/cryptsetup/
Please do not post questions there, nobody will read them. Use
the mailing-list instead.
- * Is there a mailing-list?
+ * 1.6 Is there a mailing-list?
Instructions on how to subscribe to the mailing-list are at on the
project website. People are generally helpful and friendly on the
2. Setup
- * What is the difference between "plain" and LUKS format?
+ * 2.1 What is the difference between "plain" and LUKS format?
Plain format is just that: It has no metadata on disk, reads all
paramters from the commandline (or the defaults), derives a
non-default XTS mode).
- * Can I encrypt an already existing, non-empty partition to use LUKS?
+ * 2.2 Can I encrypt an already existing, non-empty partition to use
+ LUKS?
There is no converter, and it is not really needed. The way to do
this is to make a backup of the device in question, securely wipe
to be in a filesystem.
- * How do I use LUKS with a loop-device?
+ * 2.3 How do I use LUKS with a loop-device?
This can be very handy for experiments. Setup is just the same as
with any block device. If you want, for example, to use a 100MiB
To unmap the file when done, use "losetup -d /dev/loop0".
- * When I add a new key-slot to LUKS, it asks for a passphrase but
+ * 2.4 When I add a new key-slot to LUKS, it asks for a passphrase but
then complains about there not being a key-slot with that
passphrase?
new key-slot.
- * Encrytion on top of RAID or the other way round?
+ * 2.5 Encrytion on top of RAID or the other way round?
Unless you have special needs, place encryption between RAID and
filesystem, i.e. encryption on top of RAID. You can do it the other
e.g. /dev/dm0 .
- * How do I read a dm-crypt key from file?
+ * 2.6 How do I read a dm-crypt key from file?
Note that the file will still be hashed first, just like keyboard
input. Use the --key-file option, like this:
cryptsetup create --key-file keyfile e1 /dev/loop0
- * How do I read a LUKS slot key from file?
+ * 2.7 How do I read a LUKS slot key from file?
What you really do here is to read a passphrase from file, just as
you would with manual entry of a passphrase for a key-slot. You can
cryptsetup luksOpen --key-file keyfile /dev/loop0 e1
- * How do I read the LUKS master key from file?
+ * 2.8 How do I read the LUKS master key from file?
The question you should ask yourself first is why you would want to
do this. The only legitimate reason I can think of is if you want
do this here.
- * What are the security requirements for a key read from file?
+ * 2.9 What are the security requirements for a key read from file?
A file-stored key or passphrase has the same security requirements
as one entered interactively, however you can use random bytes and
head -c 256 /dev/random > keyfile
- * If I map a journaled file system using dm-crypt/LUKS, does it still
- provide its usual transactional guarantees?
+ * 2.10 If I map a journaled file system using dm-crypt/LUKS, does it
+ still provide its usual transactional guarantees?
+
+ Yes, it does, unless a very old kernel is used. The required flags
+ come from the filesystem layer and are processed and passed onwards
+ by dm-crypt. A bit more information on the process by which
+ transactional guarantees are implemented can be found here:
- As far as I know it does (but I may be wrong), but please note that
- these "guarantees" are far weaker than they appear to be. For
- example, you may not get a hard flush to disk surface even on a
- call to fsync. In addition, the HDD itself may do independent
- write reordering. Some other things can go wrong as well. The
- filesystem developers are aware of these problems and typically
- can make it work anyways. That said, dm-crypt/LUKS should not make
- things worse.
+ http://lwn.net/Articles/400541/
- Personally, I have several instances of ext3 on dm-crypt and have
- not noticed any specific problems.
+ Please note that these "guarantees" are weaker than they appear to
+ be. One problem is that quite a few disks lie to the OS about
+ having flushed their buffers. Some other things can go wrong as
+ well. The filesystem developers are aware of these problems and
+ typically can make it work anyways. That said, dm-crypt/LUKS will
+ not make things worse.
- Update: I did run into frequent small freezes (1-2 sec) when putting
- a vmware image on ext3 over dm-crypt. This does indicate that the
- transactional guarantees are in place, but at a cost. When I went
- back to ext2, the problem went away. This also seems to have gotten
- better with kernel 2.6.36 and the reworking of filesystem flush
- locking. Kernel 2.6.38 is expected to have more improvements here.
+ One specific problem you can run into though is that you can get
+ short freezes and other slowdowns due to the encryption layer.
+ Encryption takes time and forced flushes will block for that time.
+ For example, I did run into frequent small freezes (1-2 sec) when
+ putting a vmware image on ext3 over dm-crypt. When I went back to
+ ext2, the problem went away. This seems to have gotten better with
+ kernel 2.6.36 and the reworking of filesystem flush locking
+ mechanism (less blocking of CPU activity during flushes). It
+ should improve further and eventually the problem should go away.
- * Can I use LUKS or cryptsetup with a more secure (external) medium
- for key storage, e.g. TPM or a smartcard?
+ * 2.11 Can I use LUKS or cryptsetup with a more secure (external)
+ medium for key storage, e.g. TPM or a smartcard?
Yes, see the answers on using a file-supplied key. You do have to
write the glue-logic yourself though. Basically you can have
storage.
- * Can I resize a dm-crypt or LUKS partition?
+ * 2.12 Can I resize a dm-crypt or LUKS partition?
Yes, you can, as neither dm-crypt nor LUKS stores partition size.
Whether you should is a different question. Personally I recommend
3. Common Problems
- * My dm-crypt/LUKS mapping does not work! What general steps are
+ * 3.1 My dm-crypt/LUKS mapping does not work! What general steps are
there to investigate the problem?
If you get a specific error message, investigate what it claims
the kernel. The output of "cat /proc/crypto" needs to list them.
- * My dm-crypt mapping suddenly stopped when upgrading cryptsetup.
+ * 3.2 My dm-crypt mapping suddenly stopped when upgrading cryptsetup.
The default cipher, hash or mode may have changed (the mode changed
from 1.0.x to 1.1.x). See under "Issues With Specific Versions of
cryptsetup".
- * When I call cryptsetup from cron/CGI, I get errors about unknown
- features?
+ * 3.3 When I call cryptsetup from cron/CGI, I get errors about
+ unknown features?
If you get errors about unknown parameters or the like that are not
present when cryptsetup is called from the shell, make sure you
version gets called.
- * Unlocking a LUKS device takes very long. Why?
+ * 3.4 Unlocking a LUKS device takes very long. Why?
The iteration time for a key-slot (see Section 5 for an explanation
what iteration does) is calculated when setting a passphrase. By
matter.
- * "blkid" sees a LUKS UUID and an ext2/swap UUID on the same device.
- What is wrong?
+ * 3.5 "blkid" sees a LUKS UUID and an ext2/swap UUID on the same
+ device. What is wrong?
Some old versions of cryptsetup have a bug where the header does
not get completely wiped during LUKS format and an older ext2/swap
cryptsetup luksHeaderRestore --header-backup-file <file> <device>
- * cryptsetup segfaults on Gentoo amd64 hardened ...
+ * 3.6 cryptsetup segfaults on Gentoo amd64 hardened ...
There seems to be some inteference between the hardening and and
the way cryptsetup benchmarks PBKDF2. The solution to this is
4. Troubleshooting
- * I get the error "LUKS keyslot x is invalid." What does that mean?
+ * 4.1 I get the error "LUKS keyslot x is invalid." What does that
+ mean?
This means that the given keyslot has an offset that points
outside the valid keyslot area. Typically, the reason is a
diagnosing and (if still possible) repairing this.
- * Can a bad RAM module cause problems?
+ * 4.2 Can a bad RAM module cause problems?
LUKS and dm-crypt can give the RAM quite a workout, especially when
combined with software RAID. In particular the combination RAID5 +
did a verify.
- * How do I test RAM?
+ * 4.3 How do I test RAM?
First you should know that overclocking often makes memory
problems worse. So if you overclock (which I strongly recommend
5. Security Aspects
- * Is LUKS insecure? Everybody can see I have encrypted data!
+ * 5.1 Is LUKS insecure? Everybody can see I have encrypted data!
In practice it does not really matter. In most civilized countries
you can just refuse to hand over the keys, no harm done. In some
difference between "plain" and LUKS format?"
- * Should I initialize (overwrite) a new LUKS/dm-crypt partition?
+ * 5.2 Should I initialize (overwrite) a new LUKS/dm-crypt partition?
If you just create a filesystem on it, most of the old data will
still be there. If the old data is sensitive, you should overwrite
dd if=/dev/zero of=/dev/mapper/e1
- * How do I securely erase a LUKS (or other) partition?
+ * 5.3 How do I securely erase a LUKS (or other) partition?
For LUKS, if you are in a desperate hurry, overwrite the LUKS
header and key-slot area. This means overwriting the first
dd_rescue -w /dev/zero /dev/sde1
- * How do I securely erase a backup of a LUKS partition or header?
+ * 5.4 How do I securely erase a backup of a LUKS partition or header?
That depends on the medium it is stored on. For HDD and SSD, use
overwrite with zeros. For an SSD or FLASH drive (USB stick), you
lead to data not actually being deleted at all during overwrites.
- * What about backup? Does it compromise security?
+ * 5.5 What about backup? Does it compromise security?
- That depends. See next section.
+ That depends. See item 6.7.
- * Why is all my data permanently gone if I overwrite the LUKS header?
+ * 5.6 Why is all my data permanently gone if I overwrite the LUKS
+ header?
Overwriting the LUKS header in part or in full is the most common
reason why access to LUKS containers is lost permanently.
a mapped LUKS container?" in Section "Backup and Data Recovery".
- * What is a "salt"?
+ * 5.7 What is a "salt"?
A salt is a random key-grade value added to the passphrase before
it is processed. It is not kept secret. The reason for using salts
infeasible.
- * Is LUKS secure with a low-entropy (bad) passphrase?
+ * 5.8 Is LUKS secure with a low-entropy (bad) passphrase?
Note: You should only use the 94 printable characters from 7 bit
ASCII code to prevent your passphrase from failing when the
passphrase, see next FAQ item.
Still, if you want good security, a high-entropy passphrase is the
- only option. Use at least 64 bits for secret stuff. That is 64
- characters of English text (but only if randomly chosen) or a
- combination of 12 truly random letters and digits.
+ only option. For example, a low-entropy passphrase can never be
+ considered secure against a TLA-level (Three Letter Agency level,
+ i.e. government-level) attacker, no matter what tricks are used in
+ the key-derivation function. Use at least 64 bits for secret stuff.
+ That is 64 characters of English text (but only if randomly chosen)
+ or a combination of 12 truly random letters and digits.
For passphrase generation, do not use lines from very well-known
texts (religious texts, Harry potter, etc.) as they are to easy to
and ending at a word boundary would take only something like 20
days on a single CPU and is entirely feasible. To put that into
perspective, using a number of Amazon EC2 High-CPU Extra Large
- instances (each gives about 8 real cores), this tests costs
+ instances (each gives about 8 real cores), this test costs
currently about 50USD/EUR, but can be made to run arbitrarily fast.
On the other hand, choosing 1.5 lines from, say, the Wheel of Time
this is good passphrase material.
- * What is "iteration count" and why is decreasing it a bad idea?
+ * 5.9 What is "iteration count" and why is decreasing it a bad idea?
Iteration count is the number of PBKDF2 iterations a passphrase is
put through before it is used to unlock a key-slot. Iterations are
CPU, and possibly far less.
In addition, the attacker can both parallelize and use special
- hardware like GPUs to speed up the attack. The attack can also
- happen quite some time after the luksFormat operation and CPUs can
- have become faster and cheaper. For that reason you want a bit
- of extra security. Anyways, in Example 1 your are screwed. In
- example 2, not necessarily. Even if the attack is faster, it still
- has a certain cost associated with it, say 10000 EUR/USD with
- iteration and 1 EUR/USD without iteration. The first can be
+ hardware like GPUs or FPGAs to speed up the attack. The attack can
+ also happen quite some time after the luksFormat operation and CPUs
+ can have become faster and cheaper. For that reason you want a
+ bit of extra security. Anyways, in Example 1 your are screwed.
+ In example 2, not necessarily. Even if the attack is faster, it
+ still has a certain cost associated with it, say 10000 EUR/USD
+ with iteration and 1 EUR/USD without iteration. The first can be
prohibitively expensive, while the second is something you try
- even without solid proof that the decryption will yield something
+ even without solid proof that the decryption will yield something
useful.
The numbers above are mostly made up, but show the idea. Of course
this danger significantly.
- * What about iteration count with plain dm-crypt?
+ * 5.10 Some people say PBKDF2 is insecure?
+
+ There is some discussion that a hash-function should have a "large
+ memory" property, i.e. that it should require a lot of memory to be
+ computed. This serves to prevent attacks using special programmable
+ circuits, like FPGAs, and attacks using graphics cards. PBKDF2
+ does not need a lot of memory and is vulnerable to these attacks.
+ However, the publication usually refered in these discussions is
+ not very convincing in proving that the presented hash really is
+ "large memory" (that may change, email the FAQ maintainer when it
+ does) and it is of limited usefulness anyways. Attackers that use
+ clusters of normal PCs will not be affected at all by a "large
+ memory" property. For example the US Secret Service is known to
+ use the off-hour time of all the office PCs of the Treasury for
+ password breaking. The Treasury has about 110'000 employees.
+ Asuming every one has an office PC, that is significant computing
+ power, all of it with plenty of memory for computing "large
+ memory" hashes. Bot-net operators also have all the memory they
+ want. The only protection against a resouceful attacker is a
+ high-entropy passphrase, see items 5.8 and 5.9.
+
+
+ * 5.11 What about iteration count with plain dm-crypt?
Simple: There is none. There is also no salting. If you use plain
dm-crypt, the only way to be secure is to use a high entropy
passphrase. If in doubt, use LUKS instead.
- * Is LUKS with default parameters less secure on a slow CPU?
+ * 5.12 Is LUKS with default parameters less secure on a slow CPU?
Unfortunately, yes. However the only aspect affected is the
protection for low-entropy passphrase or master-key. All other
compensate for problems in front of the keyboard.
- * Why was the default aes-cbc-plain replaced with aes-cbc-essiv?
+ * 5.13 Why was the default aes-cbc-plain replaced with aes-cbc-essiv?
The problem is that cbc-plain has a fingerprint vulnerability, where
a specially crafted file placed into the crypto-container can be
knowing the encryption key and the watermarking attack fails.
- * Are there any problems with "plain" IV? What is "plain64"?
+ * 5.14 Are there any problems with "plain" IV? What is "plain64"?
First, "plain" and "plain64" are both not secure to use with CBC,
see previous FAQ item.
does not cause any performance penalty compared to "plain".
- * What about XTS mode?
+ * 5.15 What about XTS mode?
XTS mode is potentially even more secure than cbc-essiv (but only if
cbc-essiv is insecure in your scenario). It is a NIST standard and
apply.
+ * 5.16 Is LUKS FIPS-140-2 certified?
+
+ No. But that is more a problem of FIPS-140-2 than of LUKS. From a
+ technical point-of-view, LUKS with the right parameters would be
+ FIPS-140-2 compliant, but in order to make it certified, somebody
+ has to pay real money for that. And then, whenever cryptsetup is
+ changed or extended, the certification lapses and has to be
+ obtained again.
+
+ From the aspect of actual security, LUKS with default parameters
+ should be as good as most things that are FIPS-140-2 certified,
+ although you may want to make sure to use /dev/random (by
+ specifying --use-random on luksFormat) as randomness source for
+ the master key to avoid being potentially insecure in an
+ entropy-starved situation.
+
+
6. Backup and Data Recovery
- * Why do I need Backup?
+ * 6.1 Why do I need Backup?
First, disks die. The rate for well-treated (!) disk is about 5%
per year, which is high enough to worry about. There is some
Second, for LUKS, if anything damages the LUKS header or the
key-stripe area then decrypting the LUKS device can become
- impossible. This is a frequent occuurence. For example an
+ impossible. This is a frequent occurrence. For example an
accidental format as FAT or some software overwriting the first
sector where it suspects a partition boot sector typically makes a
LUKS partition permanently inacessible. See more below on LUKS
only needs an update if you change passphrases.
- * How do I backup a LUKS header?
+ * 6.2 How do I backup a LUKS header?
While you could just copy the appropriate number of bytes from the
start of the LUKS partition, the best way is to use command option
partition creation. Example:
- cryptsetup luksHeaderBackup --header-backup-file h /dev/mapper/c1
+ cryptsetup luksHeaderBackup --header-backup-file <file> <device>
To restore, use the inverse command, i.e.
- cryptsetup luksHeaderRestore --header-backup-file h /dev/mapper/c1
+ cryptsetup luksHeaderRestore --header-backup-file <file> <device>
- * How do I backup a LUKS or dm-crypt partition?
+ * 6.3 How do I test a LUKS header?
+
+ Use
+
+ cryptsetup -v isLuks <device>
+
+ on the device. Without the "-v" it just signals its result via
+ exit-status. You can alos use the more general test
+
+ blkid -p <device>
+
+ which will also detect other types and give some more info. Omit
+ "-p" for old versions of blkid that do not support it.
+
+
+ * 6.4 How do I backup a LUKS or dm-crypt partition?
There are two options, a sector-image and a plain file or
filesystem backup of the contents of the partition. The sector
between both mounted containers. Also see next item.
- * Do I need a backup of the full partition? Would the header and
+ * 6.5 Do I need a backup of the full partition? Would the header and
key-slots not be enough?
Backup protects you against two things: Disk loss or corruption
backup to protect against this case.
- * *What do I need to backup if I use "decrypt_derived"?
+ * *6.6 What do I need to backup if I use "decrypt_derived"?
This is a script in Debian, intended for mounting /tmp or swap with
a key derived from the master key of an already decrypted device.
device with the new LUKS header.
- * Does a backup compromise security?
+ * 6.7 Does a backup compromise security?
Depends on how you do it. However if you do not have one, you are
going to eventually lose your encrypted data.
In both cases, there is an additional (usually small) risk with
binary backups: An attacker can see how many sectors and which
ones have been changed since the backup. To prevent this, use a
- filesystem level backup methid that encrypts the whole backup in
+ filesystem level backup method that encrypts the whole backup in
one go, e.g. as described above with tar and GnuPG.
My personal advice is to use one USB disk (low value data) or
is under your control...)
- * What happens if I overwrite the start of a LUKS partition or damage
- the LUKS header or key-slots?
+ * 6.8 What happens if I overwrite the start of a LUKS partition or
+ damage the LUKS header or key-slots?
There are two critical components for decryption: The salt values
in the header itself and the key-slots. If the salt values are
4-6 bits in random locations of its 128kiB size is quite enough.
- * What happens if I (quick) format a LUKS partition?
+ * 6.9 What happens if I (quick) format a LUKS partition?
I have not tried the different ways to do this, but very likely you
will have written a new boot-sector, which in turn overwrites the
damage the key-slots in part or in full. See also last item.
- * How do I recover the master key from a mapped LUKS container?
+ * 6.10 How do I recover the master key from a mapped LUKS container?
This is typically only needed if you managed to damage your LUKS
header, but the container is still mapped, i.e. "luksOpen"ed. It
You may want to disable the old one afterwards.
- * What does the on-disk structure of dm-crypt look like?
+ * 6.11 What does the on-disk structure of dm-crypt look like?
There is none. dm-crypt takes a block device and gives encrypted
access to each of its blocks with a key derived from the passphrase
overwrote.
- * What does the on-disk structure of LUKS look like?
+ * 6.12 What does the on-disk structure of LUKS look like?
A LUKS partition consists of a header, followed by 8 key-slot
descriptors, followed by 8 key slots, followed by the encrypted
http://code.google.com/p/cryptsetup/wiki/Specification
- * What is the smallest possible LUKS container?
+ * 6.13 What is the smallest possible LUKS container?
Note: From cryptsetup 1.3 onwards, alignment is set to 1MB. With
modern Linux partitioning tools that also align to 1MB, this will
alignment is not recomended.
That said, with default parameters, the data area starts at
- exactly 2MB offset (at 0x101000 for crptsetup versions before 1.3).
- The smallest data area you can have is one sector of 512 bytes.
- Data areas of 0 bytes can be created, but fail on mapping.
+ exactly 2MB offset (at 0x101000 for cryptsetup versions before
+ 1.3). The smallest data area you can have is one sector of 512
+ bytes. Data areas of 0 bytes can be created, but fail on mapping.
While you cannot put a filesystem into something this small, it may
- still be used to contain, for eamcple, key. Note that with current
+ still be used to contain, for example, key. Note that with current
formatting tools, a partition for a container this size will be
3MiB anyways. If you put the LUKS container into a file (via
losetup and a loopback device), the file needs to be 2097664 bytes
in size, i.e. 2MiB + 512B.
- The two ways to influence the start of the data area are key-size
+ There two ways to influence the start of the data area are key-size
and alignment.
For alignment, you can go down to 1 on the parameter. This will
still leave you with a data-area starting at 0x101000, i.e.
1MiB+4096B (default parameters) as alignment will be rounded up to
- the next multiple of 8 (i.e. 4096 bytes) (TODO: need to verify
- this).
+ the next multiple of 8 (i.e. 4096 bytes) If in doubt, do a dry-run
+ on a larger file and dump the LUKS header to get actual
+ information.
For key-size, you can use 128 bit (e.g. AES-128 with CBC), 256 bit
(e.g. AES-256 with CBC) or 512 bit (e.g. AES-256 with XTS mode).
- You can do 64 bit (e.g. blofish-64 with CBC), but anything below
+ You can do 64 bit (e.g. blowfish-64 with CBC), but anything below
128 bit has to be considered insecure today.
- Note: RC4 (arc4), which allows 8 bit keys, seems to be buggy at
- this time.
-
Example 1 - AES 128 bit with CBC:
cryptsetup luksFormat -s 128 --align-payload=8 <device>
266752 bytes.
- * I think this is overly complicated. Is there an alternative?
+ * 6.14 I think this is overly complicated. Is there an alternative?
Not really. Encryption comes at a price. You can use plain
dm-crypt to simplify things a bit. It does not allow multiple
borders).
+ * 6.15 Can I clone a LUKS container?
+
+ You can, but it breaks security, because the cloned container has
+ the same header and hence the same master key. You cannot change
+ the master key on a LUKS container, even if you change the
+ passphrase(s), the master key stays the same. That means whoever
+ has access to one of the clones can decrypt them all, completely
+ bypassing the passphrases.
+
+ The right way to do this is to first luksFormat the target
+ container, then to clone the contents of the source container, with
+ both containers mapped, i.e. decrypted. You can clone the decrypted
+ contents of a LUKS container in binary mode, although you may run
+ into secondary issuses with GUIDs in filesystems, partition tables,
+ RAID-components and the like. These are just the normal problems
+ binary cloning causes.
+
+ Note that if you need to ship (e.g.) cloned LUKS containers with a
+ default passphrase, that is fine as long as each container was
+ individually created (and hence has its own master key). In this
+ case, changing the default passphrase will make it secure again.
+
+
7. Interoperability with other Disk Encryption Tools
- * What is this section about?
+ * 7.1 What is this section about?
Cryptsetup for plain dm-crypt can be used to access a number of
on-disk formats created by tools like loop-aes patched into
audience may be intertested, please email the FAQ maintainer.
- * loop-aes: General observations.
+ * 7.2 loop-aes: General observations.
One problem is that there are different versions of losetup around.
loop-aes is a patch for losetup. Possible problems and deviations
give you the information you need.
- * loop-aes patched into losetup on debian 5.x, kernel 2.6.32
+ * 7.3 loop-aes patched into losetup on debian 5.x, kernel 2.6.32
In this case, the main problem seems to be that this variant of
losetup takes the offset (-o option) in bytes, while cryptsetup
mount /dev/mapper/e1 mountpoint
- * loop-aes with 160 bit key
+ * 7.4 loop-aes with 160 bit key
This seems to be sometimes used with twofish and blowfish and
represents a 160 bit ripemed160 hash output padded to 196 bit key
8. Issues with Specific Versions of cryptsetup
- * When using the create command for plain dm-crypt with cryptsetup
- 1.1.x, the mapping is incompatible and my data is not accessible
- anymore!
+ * 8.1 When using the create command for plain dm-crypt with
+ cryptsetup 1.1.x, the mapping is incompatible and my data is not
+ accessible anymore!
With cryptsetup 1.1.x, the distro maintainer can define different
default encryption modes for LUKS and plain devices. You can check
problem.
- * cryptsetup on SLED 10 has problems...
+ * 8.2 cryptsetup on SLED 10 has problems...
SLED 10 is missing an essential kernel patch for dm-crypt, which
is broken in its kernel as a result. There may be a very old