Re: Why is the chk_luks_keyslots tool not routinely included?
Robert Nichols <[email protected]>
| Newsgroups | gmane.linux.kernel.device-mapper.dm-crypt |
|---|---|
| Message-ID | <[email protected]> |
On 3/29/20 9:09 AM, Milan Broz wrote: > On 29/03/2020 14:34, Jordan Glover wrote: >> On Sunday, March 29, 2020 10:20 AM, Arno Wagner <[email protected]> wrote: >> >>> I think that is a decision by the distros. I am certainly >>> willing to maintain it for the foreseeable future. It is >>> not really much effort. >> >> The distros just do "make install" [1]. I think it's upstream who decides what this command does. >> >> [1] https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/cryptsetup#n39 > > My plan was to include this check in repair command instead of adding additional binary. > (The code could remain basically the same.) > > With LUKS2 we can store other data in binary keyslot area (depends on type), so it need a little > bit more work but it should not be a big problem. > > Please report an issue for it, that helps to not forget about it. Done. https://gitlab.com/cryptsetup/cryptsetup/-/issues/545 -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. _______________________________________________ dm-crypt mailing list [email protected] https://www.saout.de/mailman/listinfo/dm-crypt