From: Debian User <wagner@tansi.org>
Date: Thu, 23 Feb 2012 00:38:40 +0000 (+0100)
Subject: synced with wiki
X-Git-Tag: upstream/1.6~318^2
X-Git-Url: http://review.tizen.org/git/?p=platform%2Fupstream%2Fcryptsetup.git;a=commitdiff_plain;h=60d60d971a64d3cb7bdbbe5abb9e1bc3ee28c5ae

synced with wiki
---

diff --git a/FAQ b/FAQ
index 85f18e4..b41d233 100644
--- a/FAQ
+++ b/FAQ
@@ -46,7 +46,8 @@ A. Contributors
   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 can decrypt all other copies, breaking
+  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
@@ -1347,6 +1348,11 @@ http://code.google.com/p/cryptsetup/source/browse/trunk/misc/luks-header-from-ac
   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