Skip to content

Add OPAL requirement flag.

Without the OPAL requirement flag put in LUKS2 metadata it was possible to establish dm-crypt mapping over locked OPAL range with older cryptsetup releases.

Also crypt_convert action could proceed on both current branch and 2.6.1 release with opal requirement flag.

Also it is now possible to stop LUKS2 reencryption in-before we write in LUKS2 metadata. It was not serious issue but it needlessly increased sequence id in metadata and performed useless operation that can not proceed further.

Depends on !555 (merged)

Merge request reports