From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] pashphrase management question
Date: Thu, 27 Oct 2016 08:46:22 -0500 [thread overview]
Message-ID: <nut0fc$16c$1@blaine.gmane.org> (raw)
In-Reply-To: <8329bd27-e70a-99d8-5612-9277a5a4806b@whgl.uni-frankfurt.de>
On 10/27/2016 05:24 AM, Sven Eschenberg wrote:
>
>
> Am 27.10.2016 um 09:55 schrieb Arno Wagner:
>> 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 might be wrong, but changing the passphrase could make sense if (and only if) you switch the
> actual encryption key along with it by reencrypting the whole device. Aside from that changing
> passphrases seems a little pointless.
You are correct, but cryptsetup-reencrypt is a lengthy process,
during which the slightest glitch can cause you to lose everything.
It's not the sort of thing you want to be doing routinely.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
next prev parent reply other threads:[~2016-10-27 13:46 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
2016-10-27 10:24 ` Sven Eschenberg
2016-10-27 13:46 ` Robert Nichols [this message]
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='nut0fc$16c$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.