cryptsetup-2.7.5-160000.2.2

- Set pbkdf2 as the default PBKDF algorithm in LUKS2 format.
  [bsc#1236375, bsc#1236164]
  * The default PBKDF algorithm in the LUKS2 format is now Argon2id
    but its not FIPS compliant. A system would be unbootable if using
    Argon2id or Argon2i for disk encryption and then switching to
    kernel FIPS mode. This can be avoided by setting pbkdf2 as default.
  * Build using the configure option --with-luks2-pbkdf=pbkdf2.
  * Remove the dependency on libargon2 as is now provided by openssl.

- Update to 2.7.5:
  * 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.

- cryptsetup-fips140-3.patch: extend the password for PBKDF2 benchmarking
  to be more than 20 chars to meet FIPS 140-3 requirements (bsc#1229975)

- Update to 2.7.4:
  * Detect device busy failure for device-mapper table-referenced
    devices.
  * Fix shared activation for dm-verity devices.
  * Add --shared option for veritysetup open action.
  * Do not use exclusive flag for the allocated backing loop files.
  * Fixes for problems found by static analyzers and Valgrind.
  * Fixes to tests and CI scripts.
- Use fdupes to link identical man pages.

- Update to 2.7.3:
  * Do not allow formatting LUKS2 with Opal SED (hardware encryption)
    if the reported logical sector size for the block device and Opal
    encryption logical block differs.
  * Fixes to wiping LUKS2 headers after Opal locking area erase.
  * Mention the need for possible PSID revert before Opal format for some
    drives (man page).
  * Fix Bitlocker-compatible code to ignore newly seen metadata entries.
  * Fix interactive query retry if LUKS2 unbound keyslot is present.
  * Detect unsupported zoned devices for LUKS header devices.
  * Allow "capi" cipher format for benchmark command and fix parsing
    of plain IV in "capi" format.
  * Add support for HCTR2 encryption mode.
  * Source code now uses SPDX license identifiers instead of full
    license preambles.
  * Fix missing includes for cryptographic backend that could cause
    compilation errors for some systems.
  * Fix tests to work correctly in FIPS mode with recent OpenSSL 3.2.
  * Fix various (mostly false positive) issues detected by Coverity.

- License: Replace legacy 'AND SUSE-GPL-2.0-with-openssl-exception' with
  'WITH cryptsetup-OpenSSL-exception' (the official SPDX exception).

- update to 2.7.2:
  * Fix activation of OPAL-only encrypted LUKS device with tokens
  * Fix formatting of OPAL devices with 4096-byte sector size
  * Fix incorrect OPAL locking range alignment calculation if
    used over an unaligned device partition.
  * Do not check the passphrase quality for OPAL Admin PIN,
    as this passphrase already exists.
  * Update license for FAQ document to CC BY-SA 4.0.
  NOTE: Please note that with OPAL-only (--hw-opal-only)
  encryption, the configured OPAL administrator PIN (passphrase)
  allows unlocking all configured locking ranges without LUKS
  keyslot decryption (without knowledge of LUKS passphrase).
  Because of many observed problems with compatibility, cryptsetup
  currently DOES NOT use OPAL single-user mode, which would allow
  such decoupling of OPAL admin PIN access.

- Update to 2.7.1:
  * Fix interrupted LUKS1 decryption resume.
  With the replacement of the cryptsetup-reencrypt tool by the cryptsetup
  reencrypt command, resuming the interrupted LUKS1 decryption operation
  could fail. LUKS2 was not affected.
  * Allow --link-vk-to-keyring with --test-passphrase option.
  This option allows uploading the volume key in a user-specified kernel
  keyring without activating the device.
  * Fix crash when --active-name was used in decryption initialization.
  * Updates and changes to man pages, including indentation, sorting options
  alphabetically, fixing mistakes in crypt_set_keyring_to_link, and fixing
  some typos.
  * Fix compilation with libargon2 when --disable-internal-argon2 was used.
  * Do not require installed argon2.h header and never compile internal
  libargon2 code if the crypto library directly supports Argon2.
  * Fixes to regression tests to support older Linux distributions.

- Update to 2.7.0:
  * Full changelog in:
    mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.7/v2.7.0-ReleaseNotes
  * Introduce support for hardware OPAL disk encryption.
  * plain mode: Set default cipher to aes-xts-plain64 and password hashing
    to sha256.
  * Allow activation (open), luksResume, and luksAddKey to use the volume
    key stored in a keyring.
  * Allow to store volume key to a user-specified keyring in open and
    luksResume commands.
  * Do not flush IO operations if resize grows the device.
    This can help performance in specific cases where the encrypted device
    is extended automatically while running many IO operations.
  * Use only half of detected free memory for Argon2 PBKDF on systems
    without swap (for LUKS2 new keyslot or format operations).
  * Add the possibility to specify a directory for external LUKS2 token
    handlers (plugins).
  * Do not allow reencryption/decryption on LUKS2 devices with
    authenticated encryption or hardware (OPAL) encryption.
  * Do not fail LUKS format if the operation was interrupted on subsequent
    device wipe.
  * Fix the LUKS2 keyslot option to be used while activating the device
    by a token.
  * Properly report if the dm-verity device cannot be activated due to
    the inability to verify the signed root hash (ENOKEY).
  * Fix to check passphrase for selected keyslot only when adding
    new keyslot.
  * Fix to not wipe the keyslot area before in-place overwrite.
  * bitlk: Fix segfaults when attempting to verify the volume key.
  * Add --disable-blkid command line option to avoid blkid device check.
  * Add support for the meson build system.
  * Fix wipe operation that overwrites the whole device if used for LUKS2
    header with no keyslot area.
  * Fix luksErase to work with detached LUKS header.
  * Disallow the use of internal kernel crypto driver names in "capi"
    specification.
  * Fix reencryption to fail early for unknown cipher.
  * tcrypt: Support new Blake2 hash for VeraCrypt.
  * tcrypt: use hash values as substring for limiting KDF check.
  * Add Aria cipher support and block size info.
  * Do not decrease PBKDF parameters if the user forces them.
  * Support OpenSSL 3.2 Argon2 implementation.
  * Add support for Argon2 from libgcrypt
    (requires yet unreleased gcrypt 1.11).
  * Used Argon2 PBKDF implementation is now reported in debug mode
    in the cryptographic backend version. For native support in
    OpenSSL 3.2 or libgcrypt 1.11, "argon2" is displayed.
    If libargon2 is used, "cryptsetup libargon2" (for embedded
    library) or "external libargon2" is displayed.
  * Link only libcrypto from OpenSSL.
  * Disable reencryption for Direct-Access (DAX) devices.
  * Print a warning message if the device is not aligned to sector size.
  * Fix sector size and integrity fields display for non-LUKS2 crypt
    devices for the status command.
  * Fix suspend for LUKS2 with authenticated encryption (also suspend
    dm-integrity device underneath).
  * Update keyring and locking documentation and LUKS2 specification
    for OPAL2 support.
  * Remove patches fixed upstream:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch

- luksFormat: Handle system with low memory and no swap space [bsc#1211079]
  * Check for physical memory available also in PBKDF benchmark.
  * Try to avoid OOM killer on low-memory systems without swap.
  * Use only half of detected free memory on systems without swap.
  * Add patches:
  - cryptsetup-Check-for-physical-memory-available-also-in-PBKDF-be.patch
  - cryptsetup-Try-to-avoid-OOM-killer-on-low-memory-systems-withou.patch
  - cryptsetup-Use-only-half-of-detected-free-memory-on-systems-wit.patch