X7ROOT File Manager
Current Path:
/usr/share/doc/cryptsetup
usr
/
share
/
doc
/
cryptsetup
/
📁
..
📄
AUTHORS
(137 B)
📄
FAQ
(131.18 KB)
📄
v1.0.7-ReleaseNotes
(2.85 KB)
📄
v1.1.0-ReleaseNotes
(4.92 KB)
📄
v1.1.1-ReleaseNotes
(1.75 KB)
📄
v1.1.2-ReleaseNotes
(1.56 KB)
📄
v1.1.3-ReleaseNotes
(482 B)
📄
v1.2.0-ReleaseNotes
(4.74 KB)
📄
v1.3.0-ReleaseNotes
(4.64 KB)
📄
v1.3.1-ReleaseNotes
(421 B)
📄
v1.4.0-ReleaseNotes
(5.19 KB)
📄
v1.4.1-ReleaseNotes
(889 B)
📄
v1.4.2-ReleaseNotes
(1.59 KB)
📄
v1.4.3-ReleaseNotes
(2.3 KB)
📄
v1.5.0-ReleaseNotes
(8.41 KB)
📄
v1.5.1-ReleaseNotes
(1.26 KB)
📄
v1.6.0-ReleaseNotes
(9.31 KB)
📄
v1.6.1-ReleaseNotes
(1.02 KB)
📄
v1.6.2-ReleaseNotes
(985 B)
📄
v1.6.3-ReleaseNotes
(1.82 KB)
📄
v1.6.4-ReleaseNotes
(1.99 KB)
📄
v1.6.5-ReleaseNotes
(2.42 KB)
📄
v1.6.6-ReleaseNotes
(1.07 KB)
📄
v1.6.7-ReleaseNotes
(3.25 KB)
📄
v1.6.8-ReleaseNotes
(2.01 KB)
📄
v1.7.0-ReleaseNotes
(3.03 KB)
📄
v1.7.1-ReleaseNotes
(1.34 KB)
📄
v1.7.2-ReleaseNotes
(1.45 KB)
📄
v1.7.3-ReleaseNotes
(811 B)
📄
v1.7.4-ReleaseNotes
(657 B)
📄
v1.7.5-ReleaseNotes
(833 B)
📄
v2.0.0-ReleaseNotes
(26 KB)
📄
v2.0.1-ReleaseNotes
(4.75 KB)
📄
v2.0.2-ReleaseNotes
(4.07 KB)
📄
v2.0.3-ReleaseNotes
(5.21 KB)
📄
v2.0.4-ReleaseNotes
(4.9 KB)
📄
v2.0.5-ReleaseNotes
(4.3 KB)
📄
v2.0.6-ReleaseNotes
(4.16 KB)
📄
v2.1.0-ReleaseNotes
(8.68 KB)
📄
v2.2.0-ReleaseNotes
(11.61 KB)
📄
v2.2.1-ReleaseNotes
(1.38 KB)
📄
v2.2.2-ReleaseNotes
(2.1 KB)
📄
v2.3.0-ReleaseNotes
(7.79 KB)
📄
v2.3.1-ReleaseNotes
(1.73 KB)
📄
v2.3.2-ReleaseNotes
(1.46 KB)
📄
v2.3.3-ReleaseNotes
(1.36 KB)
📄
v2.3.4-ReleaseNotes
(4.33 KB)
📄
v2.3.5-ReleaseNotes
(7.25 KB)
📄
v2.3.6-ReleaseNotes
(2.26 KB)
📄
v2.3.7-ReleaseNotes
(4.42 KB)
Editing: v2.3.1-ReleaseNotes
Cryptsetup 2.3.1 Release Notes ============================== Stable bug-fix release. All users of cryptsetup 2.x should upgrade to this version. Changes since version 2.3.0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Support VeraCrypt 128 bytes passwords. VeraCrypt now allows passwords of maximal length 128 bytes (compared to legacy TrueCrypt where it was limited by 64 bytes). * Strip extra newline from BitLocker recovery keys There might be a trailing newline added by the text editor when the recovery passphrase was passed using the --key-file option. * Detect separate libiconv library. It should fix compilation issues on distributions with iconv implemented in a separate library. * Various fixes and workarounds to build on old Linux distributions. * Split lines with hexadecimal digest printing for large key-sizes. * Do not wipe the device with no integrity profile. With --integrity none we performed useless full device wipe. * Workaround for dm-integrity kernel table bug. Some kernels show an invalid dm-integrity mapping table if superblock contains the "recalculate" bit. This causes integritysetup to not recognize the dm-integrity device. Integritysetup now specifies kernel options such a way that even on unpatched kernels mapping table is correct. * Print error message if LUKS1 keyslot cannot be processed. If the crypto backend is missing support for hash algorithms used in PBKDF2, the error message was not visible. * Properly align LUKS2 keyslots area on conversion. If the LUKS1 payload offset (data offset) is not aligned to 4 KiB boundary, new LUKS2 keyslots area in now aligned properly. * Validate LUKS2 earlier on conversion to not corrupt the device if binary keyslots areas metadata are not correct.
Upload File
Create Folder