Re: [dm-crypt] bug in cryptsetup --header option when using luksFormat?

On 6/15/20 5:33 PM, Ondrej Kozina wrote:
> 
> You need to enforce --luks2-keyslots-size so that we don't use all space
> available for us. Let's say you want to have data offset at 1 GiB, but
> you'd like to have regular LUKS2 header, which is 16MiBs in total:
> 
> cryptsetup luksFormat --offset 2097152 --luks2-metadata-size 16352k
> --luks-metadata-size 16k --header headerfile containerfile

There's typo. Example should have been:

cryptsetup luksFormat --offset 2097152 --luks2-keyslots-size 16352k 
--luks2-metadata-size 16k --header headerfile containerfile

Just for the record.

> 
> (16352k is in fact 16MiB - 2*16KiB for two binary headers and two json
> metadata copies)
>