All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS2 support for null/plaintext target
Date: Fri, 13 Dec 2019 22:28:31 -0600	[thread overview]
Message-ID: <qt1odg$5hpb$1@blaine.gmane.org> (raw)
In-Reply-To: <2b1f731d-0713-fadf-f895-b62b00363a95@gmail.com>

On 12/13/19 8:59 AM, Milan Broz wrote:
> Hi,
> 
> On 07/12/2019 00:10, Chris Murphy wrote:
>> I'm wondering if it's possible, or LUKS2 could be extended, to support
>> an non-encrypted target. That is, the virtual device and backing
>> device would contain the same information.
> 
> (You are not the first one asking for support for this option.)
> 
> In fact, the support is already there. But I am reluctant to officially
> support it for a very long time, because it would be super confusing
> for users (We have LUKS, but actually no encryption?!)

How about using real encryption but use /dev/null as the key-file?
(Just a thought.)

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.

  parent reply	other threads:[~2019-12-14  4:43 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 [this message]
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
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='qt1odg$5hpb$1@blaine.gmane.org' \
    --to=rnicholsnospam@comcast.net \
    --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.