``` --- /tmp/mgorny-dev-scripts/portage/sys-fs/cryptsetup-2.7.4/work/cryptsetup-2.7.4/docs/v2.7.5-ReleaseNotes 1970-01-01 01:00:00.000000000 +0100 +++ /tmp/mgorny-dev-scripts/portage/sys-fs/cryptsetup-2.7.5/work/cryptsetup-2.7.5/docs/v2.7.5-ReleaseNotes 2024-09-02 21:52:19.000000000 +0100 @@ -0,0 +1,23 @@ +Cryptsetup 2.7.5 Release Notes +============================== +Stable bug-fix release. + +All users of cryptsetup 2.7 must upgrade to this version. + +Changes since version 2.7.4 +~~~~~~~~~~~~~~~~~~~~~~~~~~~ +* Fix possible online reencryption data corruption (only in 2.7.x). + + In some situations (initializing a suspended device-mapper device), + cryptsetup disabled direct-io device access. This caused unsafe + online reencryption operations that could lead to data corruption. + The code now adds strict checks (and aborts the operation) and + changes direct-io detection code to prevent data corruption. + +* Fix a clang compilation error in SSH token plugin. + + As clang linker treats missing symbols as errors, the linker phase + for the SSH token failed as the optional cryptsetup_token_buffer_free + was not defined. + +* Fix crypto backend initialization in crypt_format_luks2_opal API call. ``` Let's stabilise given the corruption issue mentioned.
ppc done
ppc64 done
amd64 done
x86 done
arm done
arm64 done
Unable to check for sanity: > no match for package: sys-fs/cryptsetup-2.7.5
Unable to check for sanity: > no match for package: sys-fs/cryptsetup-2.7.5-r1
All sanity-check issues have been resolved
sparc done
hppa done all arches done
