Read failure with LUKS2 with integrity algorithm and Erofs/Squashfs image
It seems that when setting a non-default integrity algorithm it's then required to specify it later when opening the volume with cryptsetup open
.
I assume this requirement will disappear as soon as an automatic detection mechanism will have be merged in cryptsetup
, so that we won't force distributions to specify one in each downstream encryption hook.
So I was wondering if meanwhile it wasn't the case to advertise the current default integrity algorithm directly in the manpage, since it's also required to specify a value when formatting a volume with luksFormat
(i.e. I have no idea), so it can easily happen that users will select a non-default without knowing about the lack of auto-detection.
Edited by tallero