Return-Path: Received: from v1.tansi.org (mail.tansi.org [84.19.178.47]) by mail.server123.net (Postfix) with ESMTP for ; Thu, 16 Apr 2020 00:25:12 +0200 (CEST) Received: from gatewagner.dyndns.org (81-6-44-245.init7.net [81.6.44.245]) by v1.tansi.org (Postfix) with ESMTPA id 678FD140211 for ; Thu, 16 Apr 2020 00:25:11 +0200 (CEST) Date: Thu, 16 Apr 2020 00:25:11 +0200 From: Arno Wagner Message-ID: <20200415222511.GB18260@tansi.org> References: <233063842.2717340.1586366160963.ref@mail.yahoo.com> <233063842.2717340.1586366160963@mail.yahoo.com> <65d9482aafb2bb4c4753f272d3c8b418c1f1d590.camel@yahoo.com> <6114e747-a8cd-c0c6-ccc8-7f666f04d32b@gmail.com> <20200411195611.GA25259@tansi.org> <20200411222340.GA26867@tansi.org> <9d06b2b9-96c5-45e7-8c1f-631e65db8bcd@localhost> <437edf2f-b68b-e904-bc28-f9a0e8021a79@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <437edf2f-b68b-e904-bc28-f9a0e8021a79@gmail.com> Subject: Re: [dm-crypt] LUKS FAQ separate for LUKS1/LUKS2, or combined? Was: cryptsetup Yubikey challenge-response support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On Tue, Apr 14, 2020 at 12:56:26 CEST, Milan Broz wrote: > On 12/04/2020 15:00, Michael Kj=F6rling wrote: > > On 12 Apr 2020 00:23 +0200, from arno@wagner.name (Arno Wagner): > >> @everybody: What are the preferences: Separate LUKS 2 FAQ or=20 > >> section in the existing FAQ?=20 > >=20 > > LUKS is LUKS. Most of the concepts are similar. Most of the problems > > LUKS (1 and 2) solve are similar.>=20 > > Yes, some _answers_ might well be different for LUKS 1 or LUKS 2. But > > the _questions_ should be mostly the same, and _why_ to do one thing > > or another should be similar. The only obvious exception to that which > > I can think of is where something is _possible_ in LUKS 2, but simply > > not possible in LUKS 1, _and_ that would be worthy of inclusion in a > > FAQ in the first place. >=20 > Yes, and in fact we designed LUKS2 to be compatible as possible > and it is described in LUKS2 doc, referenced from FAQ already). >=20 > So, there should be only one FAQ. > (And for upstream, I am not going to support any doc split in > released archive. That would be confusing to users. They should > not care about version, unless they use some new feature.) Ok, I think that is settled then: Current FAQ will be updated in order to have one place of reference and to not have=20 redundancies (where possible). =20 > What we need to do is to use only one FAQ copy (currently there is text > version in main repo and primary version in wiki git), the wiki version > is already in markdown format, so perhaps I can move it to the > main git repo and this allows easy contributions through merge requests. > (The same problem applies for README, it is confusing to have two version= s.) Since I have always only maintained the Wiki version (I still have the Wiki->txt Python script somewhere, I think) that is entirely fine by me. > (Unfortunately Gitlab does not allow to open merge request to wiki pages, > so to be open to direct contributions, keeping it in main repo is simpler= .) Just let me know what you decide. Since it looks like I will be doing=20 some editing, it would be nice if I could still edit it directly though. Of course I do not need (or want) access to anything else. =20 > > There's already parts in the FAQ that discuss dm-crypt, RAM, > > passphrases, erasing data, and so on; so there's ample precedent that > > the FAQ already covers more than LUKS (1) proper. >=20 > And some of these need update too, for example use of kernel keyring > makes all scripts that use key in mapping table obsolete. > (This is a dm-crypt feature, not LUKS2 one.) Ok. Here I would need to know what heppens if the kernel is old=20 and does not have the keyring feature. Or is the keyring feature=20 assured on all currently maintained kernels? First document I found=20 on it on a brief search is from 2006, so that may be the case. Since this seems to be originally for eCryptFS (which I do not use), I have ignored this feature so far. Is https://www.kernel.org/doc/Documentation/security/keys-ecryptfs.txt the autorative reference? Or am I confusing something here? > > Therefore, in the name of consistency and ease of reading, I would > > suggest to keep it all in one document, _but_ clearly mark the parts > > that only apply to one or the other. (This could be whole Q/A tuples, > > or just a portion such as an example command line.) Also perhaps add > > something near the top for how to tell based on an existing container, > > ideally irrespective of how the distribution does things, whether a > > LUKS container is LUKS 1 or LUKS 2. >=20 > I do not think is so big problem. >=20 > LUKS2 format allows many optional features (authenticated encryption, > reencryption, token metadata store), but these should be in separate > chapter anyway. I agree. "Section XYZ: Additional features available with LUKS2". > The basic functionality is exactly the same as LUKS1, just it allows more > flexibility (more keyslot, other PBKDF etc). >=20 > Also, if you anyone think there missing anything in LUKS2 doc, please > be exact and report it. Yes, please do. And on things added to the FAQ, please report errors. > GRUB2 just implemented LUKS2 support using that doc, so I think > it works as implementation doc. > (And the cryptography is exactly the same as in LUKS1, except Argon2 PBKD= F.) Ah, good to know. That was one of the things unclear to me. Another item for the LUKS2 section. Ok, I think I can invest a few hours this or next weekend to=20 start on the structure additions to the FAQ and put in some=20 initial items and do some reviewe.=20 The whole process will take a while though. Regards, Arno =20 > Milan > _______________________________________________ > dm-crypt mailing list > dm-crypt@saout.de > https://www.saout.de/mailman/listinfo/dm-crypt --=20 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=20 "news" is "something that hardly ever happens." -- Bruce Schneier