Blame docs/v2.2.1-ReleaseNotes

Packit 94f725
Cryptsetup 2.2.1 Release Notes
Packit 94f725
==============================
Packit 94f725
Stable bug-fix release.
Packit 94f725
Packit 94f725
This version contains a fix for a possible data corruption bug
Packit 94f725
on 32-bit platforms.
Packit 94f725
All users of cryptsetup 2.1 and 2.2 should upgrade to this version.
Packit 94f725
Packit 94f725
Changes since version 2.2.0
Packit 94f725
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Packit 94f725
Packit 94f725
* Fix possible data length and IV offset overflow on 32bit architectures.
Packit 94f725
  Other 64-bit architectures are not affected.
Packit 94f725
Packit 94f725
  The flawed helper function prototypes (introduced in version 2.1.0) used
Packit 94f725
  size_t type, that is 32-bit integer on 32-bit systems.
Packit 94f725
  This patch fixes the problem to properly use 64-bit types.
Packit 94f725
Packit 94f725
  If the offset parameter addresses devices larger than 2TB, the value
Packit 94f725
  overflows and stores incorrect information in the metadata.
Packit 94f725
  For example, integrity device is smaller than expected size if used
Packit 94f725
  over large disk on 32-bit architecture.
Packit 94f725
Packit 94f725
  This issue is not present with the standard LUKS1/LUKS2 devices without
Packit 94f725
  integrity extensions.
Packit 94f725
Packit 94f725
* Fix a regression in TrueCrypt/VeraCrypt system partition activation.
Packit 94f725
Packit 94f725
* Reinstate missing backing file hint for loop device.
Packit 94f725
Packit 94f725
  If the encrypted device is backed by a file (loopback), cryptsetup now
Packit 94f725
  shows the path to the backing file in passphrase query (as in 1.x version).
Packit 94f725
Packit 94f725
* LUKS2 reencryption block size is now aligned to reported optimal IO size.
Packit 94f725
  This change eliminates possible non-aligned device warnings in kernel log
Packit 94f725
  during reencryption.