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] LUKS2 support for null/plaintext target
Date: Mon, 16 Dec 2019 19:49:36 +0100	[thread overview]
Message-ID: <20191216184935.GA17227@tansi.org> (raw)
In-Reply-To: <CAJCQCtRu0hn34JGN+MvRoDXg3ri9aUi9Y+gD6kuSKYvj=nxV-Q@mail.gmail.com>

On Mon, Dec 16, 2019 at 19:24:33 CET, Chris Murphy wrote:
[...]
> But consider that as a direct consequence of the burden to
> backup->luksFormat>restore, quite a lot of users opt out of encryption
> entirely. The point of in-place conversion isn't perfect security.
> It's to get more users to opt in, by reducing the penalty of opting
> in.

But why would you _want_ users to "opt in"? It seems like entirely
the wrong thing to do to me. First consider that the users 
you are talking about do not have backups. Hence their data must
be basically worthless anyways! Second, their data is so little
in need of protection that something as simple and as a backup  
already makes them do without encryption. Hence their data must
actually not be sensitive in any way!

Given these two things, why on earth do you want these people
to use encryption?

Security comes at a price. That price has to be paid. 
No price - no security. There is _no_ way to fix this and trying 
to do so only does damage to the user by making things too complex
for them to handle.

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:[~2019-12-16 18:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 23:10 [dm-crypt] LUKS2 support for null/plaintext target Chris Murphy
2019-12-07  9:39 ` Michael Kjörling
2019-12-08 16:59   ` Chris Murphy
2019-12-13 14:59 ` Milan Broz
2019-12-13 18:54   ` Chris Murphy
2019-12-13 21:41     ` Arno Wagner
2019-12-14  4:28   ` Robert Nichols
2019-12-14 14:42     ` Arno Wagner
2019-12-14 21:18       ` Chris Murphy
2019-12-15 17:51         ` Jordan Glover
2019-12-15 19:12           ` Arno Wagner
2019-12-15 20:49           ` Chris Murphy
2019-12-16 17:08             ` Jordan Glover
2019-12-16 18:24               ` Chris Murphy
2019-12-16 18:49                 ` Arno Wagner [this message]
2019-12-16 20:46                   ` Chris Murphy
2019-12-16 22:08                     ` Arno Wagner
2019-12-16 21:33                 ` Michael Kjörling
2019-12-16 22:17                   ` Chris Murphy
2019-12-17 17:07                 ` Jordan Glover
2019-12-18  0:24                   ` 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=20191216184935.GA17227@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.