From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Why is it necessary to "wipe" an authenticated luks2 device when creating it?
Date: Fri, 27 Sep 2019 00:20:06 +0200 [thread overview]
Message-ID: <20190926222005.GA6425@tansi.org> (raw)
In-Reply-To: <qmjag0$39d1$1@blaine.gmane.org>
On Thu, Sep 26, 2019 at 23:27:27 CEST, Robert Nichols wrote:
> I wasn't even thinking of trim pass-through. I routinely set up VMs with
> space allocations that, in total, exceed the space available on the host.
> Such VMs cannot use authenticated encryption since they would have to
> immediately use all of their allocated space. I also routinely save
> system images with partclone or clonezilla, specifically to avoid saving
> the content of the free space in the filesystems. Such an image would
> fail authentication when restored. These are fairly common practices.
> LUKS2 authenticated encryption should come with huge warnings.
I think a regular explanation what authenticated encryption
does (to those that do not know it) should be entirely enough.
The behavior is not in any way surprising, after all.
Add to that that it is not the default and there is no
need for any "huge warnings". People that do not knwo what
they are doing will shoot themselves in the foot anyways.
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:[~2019-09-26 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 19:40 [dm-crypt] Why is it necessary to "wipe" an authenticated luks2 device when creating it? .. ink ..
2019-09-26 7:41 ` Milan Broz
2019-09-26 9:36 ` Christoph Anton Mitterer
2019-09-26 13:38 ` Robert Nichols
2019-09-26 14:29 ` Ondrej Kozina
2019-09-26 21:27 ` Robert Nichols
2019-09-26 22:20 ` Arno Wagner [this message]
2019-09-27 8:52 ` Milan Broz
2019-09-26 14:23 ` Arno Wagner
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=20190926222005.GA6425@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox