From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from blaine.gmane.org (195-159-176-226.customer.powertech.no [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Sat, 14 Dec 2019 05:43:42 +0100 (CET) Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1ifz2k-000lU3-Sk for dm-crypt@saout.de; Sat, 14 Dec 2019 05:28:38 +0100 From: Robert Nichols Date: Fri, 13 Dec 2019 22:28:31 -0600 Message-ID: References: <2b1f731d-0713-fadf-f895-b62b00363a95@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <2b1f731d-0713-fadf-f895-b62b00363a95@gmail.com> Content-Language: en-US Subject: Re: [dm-crypt] LUKS2 support for null/plaintext target List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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.