All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt
Date: Fri, 16 Jun 2017 20:35:17 +0200	[thread overview]
Message-ID: <20170616183517.GA9583@tansi.org> (raw)
In-Reply-To: <20170616144715.GC11824@yeono.kjorling.se>

On Fri, Jun 16, 2017 at 16:47:15 CEST, Michael Kjörling wrote:
> On 16 Jun 2017 16:31 +0200, from arno@wagner.name (Arno Wagner):
[...]
> And of course, for those who use FDE to facilitate storage device
> decommissioning (just throw away the key and the data is effectively
> unreadable), the _knowledge_ that _all_ data that touches the storage
> device is encrypted before it does might even be the whole _point_ of
> using FDE.

That may actually be critical in an enterprise-scenario. 
As in "do not use anything that does not have this property",
enforced by a policy. 

> But I'm preaching to the choir, here. Or at least I hope I am.

You are. I think this whole thing is just another instance of
some crypto-novices to "improve" things. They usually do not 
understand what the crypto actually assures and how easily that 
can be broken. The only thing to do is (once again) explain
why this is a bad idea.

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

  reply	other threads:[~2017-06-16 18:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 23:40 [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt Michael Halcrow
2017-06-14 23:40 ` [RFC PATCH 1/4] block: Add bio req flag to disable encryption in block Michael Halcrow
2017-06-14 23:40 ` [RFC PATCH 2/4] dm-crypt: Skip encryption of file system-encrypted blocks Michael Halcrow
2017-06-14 23:40 ` [RFC PATCH 3/4] ext4: Set the bio REQ_NOENCRYPT flag Michael Halcrow
2017-06-14 23:40 ` [RFC PATCH 4/4] f2fs: " Michael Halcrow
2017-06-15  7:33 ` [dm-crypt] [RFC PATCH 0/4] Allow file systems to selectively bypass dm-crypt Milan Broz
2017-06-15  7:33   ` Milan Broz
2017-06-15 17:24   ` [dm-crypt] " Michael Halcrow
2017-06-15 17:24     ` Michael Halcrow
2017-06-15 18:17     ` [dm-crypt] " Milan Broz
2017-06-15 18:17       ` Milan Broz
2017-06-16 18:42       ` [dm-crypt] " Michael Halcrow
2017-06-16 18:42         ` Michael Halcrow
2017-06-20 14:44         ` [dm-crypt] " Mike Snitzer
2017-06-20 14:44           ` Mike Snitzer
2017-06-16 12:55     ` [dm-crypt] " Michael Kjörling
2017-06-16 14:31       ` Arno Wagner
2017-06-16 14:47         ` Michael Kjörling
2017-06-16 18:35           ` Arno Wagner [this message]
2017-06-16 10:34   ` Daniel P. Berrange
2017-06-16 14:02   ` 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=20170616183517.GA9583@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.