From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <chris@colorremedies.com>
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com
 [IPv6:2a00:1450:4864:20::42a])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sat,  7 Dec 2019 00:10:54 +0100 (CET)
Received: by mail-wr1-x42a.google.com with SMTP id z7so9424447wrl.13
 for <dm-crypt@saout.de>; Fri, 06 Dec 2019 15:10:54 -0800 (PST)
MIME-Version: 1.0
From: Chris Murphy <lists@colorremedies.com>
Date: Fri, 6 Dec 2019 16:10:37 -0700
Message-ID: <CAJCQCtSUtmf1wOs=ecch-EioqT5isLOyyw5aZhJ3RXjRL3mLBg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Subject: [dm-crypt] LUKS2 support for null/plaintext target
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

Hi,

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.

The use case is to make it possible for software installers to make
future encryption possible for a volume without need to
repartition/reformat.

Thanks,

-- 
Chris Murphy