From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] pashphrase management question
Date: Thu, 27 Oct 2016 09:55:35 +0200 [thread overview]
Message-ID: <20161027075535.GA4754@tansi.org> (raw)
In-Reply-To: <nurdik$df4$1@blaine.gmane.org>
On Thu, Oct 27, 2016 at 01:17:42 CEST, Robert Nichols wrote:
> 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.
This is probably just the usual "cargo-cult" security, i.e.
follow the ritual (a.k.a. "Process") without question,
because that would require understanding.
Regular passphrase changes on storage-encryption make
absolutely no sense and gives you absolutely no
protection benefit (unless you have told somebody
that should not know, in which case you need to change
them immediately).
I would try to give "them" a definition of the LUKS
passphrase that does not make it a "password" or
"login credential", and with a bit of luck you can
negate thereby prevent the usuall "password" process
and its requirements from applying.
One approach would be to make this a "technical secret"
or the like. After all, they probably to not require,
say, passphrases protecting certificates to be changed
regularly, because that would be relatively difficult.
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2016-10-27 7:55 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
2016-10-27 7:55 ` Arno Wagner [this message]
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=20161027075535.GA4754@tansi.org \
--to=arno@wagner.name \
--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.