On 11/04/2020 21:56, Arno Wagner wrote: > On Sat, Apr 11, 2020 at 18:09:46 CEST, Milan Broz wrote: >> On 11/04/2020 16:49, JT Moree wrote: >>> Arno is working on updating the docs for new features of luks2. >> >> Arno did not add anything to FAQ in this regard for the last two+ years (the last >> contribution was in 2017, I do not count last week change for "LUKS2 is not >> covered" FAQ commit. >> The FAQ is really obsolete now, and we have to update it or remove it >> from distribution soon. >> (Many people already complained through various channels.) > > Well, many people complained and exactly zero did any work > or offered any work. Also, zero did complain to me (except > for the comments on the list here). These two details make > me very unconcerned about their complaints. Arno, please do not take this as a personal thing. There are several issues in tracker about FAQ, some distributions already have quite nice own LUKS2 doc (Arch Linux for example). So we should update it, even it is incomplete, it is better than to not touch it at all. Also, external contributors should have easy way hot to update FAQ (see my other reply about wiki; merge request are not problematic). > This is, at the moment, the LUKS 1 FAQ (and that was really > what the commit from last week was about), and as that it does > not need removing. It also covers quite a bit of stuff that is > not LUKS 1 specific and some stuff that is not even LUKS specific. > So unless you are positive nobody uses LUKS 1 anymore, and the > not LUKS 1 specific stuff is irrelevant, removing it would really > be the wrong approach. Yes, LUKS1 is there and will be there. But what I really tried from the beginning - a normal user should not care about version. (For example that keyslot checker use API, so it should work with LUKS2 etc. Just the offsets of keyslot will not be fixed.) And it works this way, people complained mainly about memory requirements for Argon KDF (and that is a feature, not a bug :-) > If you want to start a LUKS 2 FAQ, be my guest. But be aware > that such a thing is a _lot_ of work before it is anywhere > near completion. That you do not have complete design > documentation for LUKS 2 (as far as I can tell) makes it > even harder. Maybe you write that documentation and as soon > as it is complete, I will go into the FAQ and start updating. One LUKS FAQ is enough for anyone :) What is missing in LUKS2 doc that you need for this work to start? It is metadata on-disk format, nothing more. And for the FAQ complexity - I am FAQ co-author since the cryptsetup 1.0.7 (2009) release so I know how longterm work it is. That's why it a little bit irritates me that we did not updated it yet (I just fixed obsolete links there). Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx https://www.saout.de/mailman/listinfo/dm-crypt
