From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] The future of disk encryption with LUKS2
Date: Fri, 5 Feb 2016 20:45:35 +0100 [thread overview]
Message-ID: <20160205194535.GA2073@tansi.org> (raw)
In-Reply-To: <56B4C342.1080505@gmail.com>
On Fri, Feb 05, 2016 at 16:44:02 CET, Milan Broz wrote:
> On 02/05/2016 04:24 PM, Arno Wagner wrote:
> > On Fri, Feb 05, 2016 at 16:01:14 CET, Yves-Alexis Perez wrote:
> >> On ven., 2016-02-05 at 14:31 +0100, Arno Wagner wrote:
> >>> No. You are trying to solve the wrong problem. First, disk
> >>> encryption with 1:1 mapping will never give you integrity
> >>> protection and the other variants kill performance.
> >>
> >> I perfectly understand that, thank you. Again, I'm *well aware* of the need to
> >> store integrity patterns somewhere. I'm *not* asking for 1:1 mapping.
> >>
> >> Can I sincerely ask that you not consider at first (and second, and third)
> >> that I didn't think first about what I was asking on the list?
> >
> > Then why are you asking about integrity protection on a list
> > dedicated to a block-layer encryption system? That does not make
> > any sense. If you state things that do not make sense then I
> > will point that out, because there is a real possibility that
> > your reasoning process (I am not implying there was none) was
> > flawed.
>
> I think it is perfectly fine to ask there (please do not forget
> we are still closely cooperating with storage guys).
It is fine to ask. But if you get your hackles up when being
told "not really", that is something else.
> And by the way, we have a experimental plan to test authenticated
> encryption on this level (obviously part of that is to solve additional
> metadata space). (Even if it is not usable in the end I would like to try
> that.)
Sure, it would be interesting to see how badly this impacts
performance, for example.
> The reply/revert attack possibility without support of specific hw will
> be still there but I would say even if we can provide method how to detect
> random corruption of sectors it could be useful.
From my experience with larger storage systems, I doubt that.
The disks do an excellent job of detecting sector corruption
themselves these days. And even before, a defective CPU or RAM
was much more likely the cause of data corruption than an
undetected read error on disk.
As it is basically free with authenticated encryption, it may
still have some use though.
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-02-05 19:45 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 13:13 [dm-crypt] The future of disk encryption with LUKS2 .. ink ..
2016-02-03 14:02 ` Yves-Alexis Perez
2016-02-03 14:17 ` Milan Broz
2016-02-03 17:07 ` Arno Wagner
2016-02-03 19:46 ` Sven Eschenberg
2016-02-04 8:38 ` Milan Broz
2016-02-04 9:20 ` Michael Kjörling
2016-02-04 10:02 ` Milan Broz
2016-02-04 11:01 ` Arno Wagner
2016-02-04 16:34 ` Sven Eschenberg
2016-02-04 17:23 ` Arno Wagner
2016-02-04 18:42 ` Michael Kjörling
2016-02-04 20:51 ` Sven Eschenberg
2016-02-05 10:56 ` Arno Wagner
2016-02-05 15:08 ` Robert Nichols
2016-02-05 15:57 ` Arno Wagner
2016-02-05 23:51 ` Sven Eschenberg
2016-02-06 2:58 ` Arno Wagner
2016-02-06 3:18 ` Sven Eschenberg
2016-02-06 10:01 ` Michael Kjörling
2016-02-06 14:29 ` Arno Wagner
2016-02-06 18:56 ` Sven Eschenberg
2016-02-06 19:09 ` Michael Kjörling
2016-02-06 19:18 ` Sven Eschenberg
2016-02-07 0:09 ` Lars Winterfeld
2016-02-07 23:05 ` Arno Wagner
2016-02-08 0:25 ` Sven Eschenberg
2016-02-08 11:34 ` Michael Kjörling
2016-02-08 16:57 ` Arno Wagner
2016-02-08 20:19 ` f-dm-c
2016-02-08 16:41 ` Arno Wagner
2016-02-08 17:26 ` Sven Eschenberg
2016-02-08 18:49 ` Arno Wagner
2016-02-08 19:08 ` Sven Eschenberg
2016-02-08 20:31 ` f-dm-c
2016-02-08 20:51 ` Sven Eschenberg
2016-02-08 21:10 ` Arno Wagner
2016-02-08 21:43 ` f-dm-c
2016-02-08 22:04 ` Sven Eschenberg
2016-02-08 21:08 ` Arno Wagner
2016-02-08 21:45 ` f-dm-c
2016-02-06 14:20 ` Arno Wagner
2016-02-06 19:13 ` Sven Eschenberg
2016-02-07 7:09 ` f-dm-c
2016-02-07 23:17 ` Arno Wagner
2016-02-08 0:40 ` Sven Eschenberg
2016-02-08 2:06 ` f-dm-c
2016-02-08 2:46 ` Sven Eschenberg
2016-02-08 3:43 ` f-dm-c
2016-02-08 4:32 ` Sven Eschenberg
2016-02-08 6:09 ` f-dm-c
2016-02-08 16:51 ` Arno Wagner
2016-02-08 20:05 ` f-dm-c
2016-02-08 20:11 ` f-dm-c
2016-02-08 20:35 ` Sven Eschenberg
2016-02-08 17:27 ` Sven Eschenberg
2016-02-08 16:48 ` Arno Wagner
2016-02-08 19:49 ` f-dm-c
2016-02-08 19:57 ` Arno Wagner
2016-02-08 20:05 ` Sven Eschenberg
2016-02-04 9:35 ` Sumaya1960
2016-02-04 10:48 ` Arno Wagner
[not found] ` <56B4AC42.7070408@gmx.de>
2016-03-01 12:50 ` [dm-crypt] LUKS NVMe M.2 SSD - save disklayout Sumaya1960
2016-03-01 18:18 ` Sven Eschenberg
2016-03-04 22:05 ` doark
2016-03-10 12:13 ` Matthias Schniedermeyer
2016-03-14 18:23 ` Sven Eschenberg
2016-02-04 16:29 ` [dm-crypt] The future of disk encryption with LUKS2 Yves-Alexis Perez
2016-02-04 17:17 ` Arno Wagner
2016-02-05 6:30 ` Yves-Alexis Perez
2016-02-05 11:02 ` Arno Wagner
2016-02-05 13:13 ` Yves-Alexis Perez
2016-02-05 13:31 ` Arno Wagner
2016-02-05 15:01 ` Yves-Alexis Perez
2016-02-05 15:24 ` Arno Wagner
2016-02-05 15:44 ` Milan Broz
2016-02-05 19:45 ` Arno Wagner [this message]
2016-02-05 22:43 ` Arno Wagner
2016-02-05 16:50 ` Yves-Alexis Perez
2016-02-05 19:53 ` Arno Wagner
2016-02-05 21:09 ` Arno Wagner
[not found] ` <20160205133123.GA31320@das-labor.org>
2016-02-05 13:49 ` Zaolin
2016-02-05 15:15 ` Arno Wagner
2016-02-08 21:51 ` Milan Broz
2016-02-08 22:36 ` Sven Eschenberg
2016-02-09 0:27 ` Milan Broz
2016-02-09 1:02 ` Arno Wagner
2016-02-09 22:08 ` Lars Winterfeld
2016-02-09 23:35 ` Arno Wagner
2016-02-10 0:20 ` Sven Eschenberg
2016-02-10 8:37 ` Milan Broz
2016-02-10 11:47 ` Arno Wagner
2016-02-10 13:48 ` Sven Eschenberg
2016-02-10 14:35 ` Robert Nichols
2016-02-10 15:09 ` Sven Eschenberg
2016-02-10 15:39 ` Milan Broz
2016-02-10 16:22 ` Arno Wagner
2016-02-10 17:13 ` Sven Eschenberg
2016-02-10 16:48 ` Sven Eschenberg
2016-02-11 5:09 ` Robert Nichols
2016-02-11 6:44 ` Milan Broz
2016-02-14 8:20 ` Milan Broz
2016-02-14 21:32 ` Sven Eschenberg
-- strict thread matches above, loose matches on Subject: below --
2016-03-12 21:20 David Niklas
2016-03-16 6:36 ` Ondrej Kozina
2016-03-25 21:09 ` David Niklas
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=20160205194535.GA2073@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.