"Fossies" - the Fresh Open Source Software Archive

Member "cryptsetup-2.4.3/docs/v2.3.2-ReleaseNotes" (13 Jan 2022, 1499 Bytes) of package /linux/misc/cryptsetup-2.4.3.tar.xz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 Cryptsetup 2.3.2 Release Notes
    2 ==============================
    3 Stable bug-fix release.
    4 
    5 All users of cryptsetup 2.x should upgrade to this version.
    6 
    7 Changes since version 2.3.1
    8 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    9 
   10 * Support compilation with json-c library version 0.14.
   11 
   12 * Update FAQ document for some LUKS2 specific information.
   13 
   14 * Add option to dump content of LUKS2 unbound keyslot:
   15     cryptsetup luksDump --unbound -S <slot> <device>
   16   or optionally with --master-key-file option.
   17 
   18   The slot number --key-slot (-S) option is mandatory here.
   19 
   20   An unbound keyslot store a key is that is not assigned to data
   21   area on disk (LUKS2 allows to store arbitrary keys).
   22 
   23 * Rephrase some error messages and remove redundant end-of-lines.
   24 
   25 * Add support for discards (TRIM) for standalone dm-integrity devices.
   26   Linux kernel 5.7 adds support for optional discard/TRIM operation
   27   over dm-integrity devices.
   28 
   29   It is now supported through --allow-discards integritysetup option.
   30   Note you need to add this flag in all activation calls.
   31 
   32   Note that this option cannot be used for LUKS2 authenticated encryption
   33   (that uses dm-integrity for storing additional per-sector metadata).
   34 
   35 * Fix cryptsetup-reencrypt to work on devices that do not allow
   36   direct-io device access.
   37 
   38 * Fix a crash in the BitLocker-compatible code error path.
   39 
   40 * Fix Veracrypt compatible support for longer (>64 bytes) passphrases.
   41   It allows some older images to be correctly opened again.
   42   The issue was introduced in version 2.3.1.