DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Mosesohn <mmosesoh@redhat.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Security of cloned disks (with changed passphrases)
Date: Thu, 16 Dec 2010 13:27:04 -0500 (EST)	[thread overview]
Message-ID: <1161837945.960861292524024535.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <930971623.959051292522978225.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 663 bytes --]


I am wondering if I perform this setup (cryptsetup version 1.1.2), how much risk do I expose my systems to? 

Step 1: Create a base install that is encrypted with a fixed passphrase 
Step 2: Create a disk image of this installed system 
Step 3: Deploy image on N number of other systems 
Step 4: Change the passphrase on all deployed systems 

What happens if the passphrase becomes compromised on one of these systems? Can that person gain the original LUKS AES key to the disk and therefore obtain a way to break into all of the other systems? 

If yes, is there anything to do on each cloned system to improve security? 

-- 
Best Regards, 
Matthew Mosesohn 

[-- Attachment #2: Type: text/html, Size: 985 bytes --]

  reply	other threads:[~2010-12-16 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <175017369.959011292522941452.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-12-16 18:09 ` [dm-crypt] Security of cloned disks (with changed passphrases) Matthew Mosesohn
2010-12-16 18:27   ` Matthew Mosesohn [this message]
2010-12-16 19:11     ` Milan Broz
2010-12-17  4:54     ` Nargis Khan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1161837945.960861292524024535.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com \
    --to=mmosesoh@redhat.com \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox