On 02/03/2019 11:23, Christoph Biedl wrote:
> Thanks for looking into this and the insights given. For luksmeta
> however ... it's "to access metadata in a LUKSv1 header", and before the
> buster release I better shall refrain from checking how the related
> tools like clevis deal with LUKSv2
Guilhem Moulin wrote...
> FWIW the regression isn't directly tied to the new default LUKS format,
> but to the PBKDF benchmark for Argon2i/id (the default PBKDF for LUKS2).
> Here is an output snippet obtained with --debug:
(...)
> Anyway, IMHO in test scenari it makes sense to the PBKDF
Control: found -1 2:2.1.0-1
Hi Christoph,
On Fri, 01 Mar 2019 at 11:09:53 +0100, Christoph Biedl wrote:
> Declare usage of format 1 like in
>
> $ echo -n foo | cryptsetup luksFormat --type luks1 /tmp/blob -
>
> and possibly some other ways.
FWIW the regression isn't directly tied to the new
3 matches
Mail list logo
