All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] pashphrase management question
Date: Wed, 26 Oct 2016 18:17:42 -0500	[thread overview]
Message-ID: <nurdik$df4$1@blaine.gmane.org> (raw)
In-Reply-To: <b26cede38d7591ddae6a4a82518e0f32.squirrel@webmail.lookafish.com>

On 10/26/2016 11:43 AM, ClEmFoster wrote:
> hello,
>
> The setup:
>
> I work in an environment that has a whole disk encryption requirement for
> VMs.  If the VM is restarted an admin has to hit the console and type in
> the passphrase to boot.  This is OK, we don't reboot much, and security
> guys are happy.  The problem is they are going to start requiring that
> these machines also receive a passphrase change every 3 or 6 months.  That
> brings me to the question.

Are "they" aware that anyone who has had read access to the device
with the LUKS container has had an opportunity to copy the LUKS
header, and can always use that LUKS header with the old passphrase
to unlock the container (perhaps after spending however much time
and processing power is needed to crack that passphrase offline).

For that matter, anyone with root access to the VM while the LUKS
container is unlocked can easily obtain the master key
(dmsetup table --showkeys /dev/{whatever}) and can always access
the LUKS container with that.

Changing the passphrase doesn't protect against any of that.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.

  parent reply	other threads:[~2016-10-26 23:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 16:43 [dm-crypt] pashphrase management question ClEmFoster
2016-10-26 20:39 ` Michael Kjörling
2016-10-26 21:08   ` ClEmFoster
     [not found]     ` <8a3e5971-3437-5c0f-6d37-f3043a0918b9@whgl.uni-frankfurt.de>
2016-10-26 21:40       ` ClEmFoster
2016-10-26 21:55       ` Michael Kjörling
2016-10-26 23:17 ` Robert Nichols [this message]
2016-10-27  7:55   ` Arno Wagner
2016-10-27 10:24     ` Sven Eschenberg
2016-10-27 13:46       ` Robert Nichols
2016-10-27 16:14         ` ClEmFoster

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='nurdik$df4$1@blaine.gmane.org' \
    --to=rnicholsnospam@comcast.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.