All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: Chris Murphy <lists@colorremedies.com>
Cc: "dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] LUKS2 support for null/plaintext target
Date: Sun, 15 Dec 2019 17:51:00 +0000	[thread overview]
Message-ID: <Kuf0HqfNDFs36S39f45WW2TuxKIdYzTr0QkObdzLaUYeY2s58O5BPCwXLBK43xVi1E7pXvVZ3zD12KLVkAU7V3a03Gu6-eIo4PtVts8rDA4=@protonmail.ch> (raw)
In-Reply-To: <CAJCQCtQ4YWh0+4vbHPKF9kL=g0_0G7xpZsY7xnSJffTn_HPWsg@mail.gmail.com>

I think encrypting previously unencrypted data on the same disk
doesn't guarantee that old data won't be recoverable especially
on ssd/nvme which are ubiquitous today. Officially supporting
such case on LUKS will give users false sense of security of
their data.

Jordan

  reply	other threads:[~2019-12-15 18:00 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 [this message]
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
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='Kuf0HqfNDFs36S39f45WW2TuxKIdYzTr0QkObdzLaUYeY2s58O5BPCwXLBK43xVi1E7pXvVZ3zD12KLVkAU7V3a03Gu6-eIo4PtVts8rDA4=@protonmail.ch' \
    --to=golden_miller83@protonmail.ch \
    --cc=dm-crypt@saout.de \
    --cc=lists@colorremedies.com \
    /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.