FM / cryptsetup

/usr/share/doc/cryptsetup

Name	Size	Mode	Actions
examples/	-	0755	rm
AUTHORS	137	0644	edit dl rm
changelog.Debian.gz	2251	0644	edit dl rm
copyright	9292	0644	edit dl rm
FAQ.gz	48990	0644	edit dl rm
Keyring.txt	2724	0644	edit dl rm
LUKS2-locking.txt	2711	0644	edit dl rm
NEWS.Debian.gz	1057	0644	edit dl rm
README.Debian.gz	5680	0644	edit dl rm
README.debug	2731	0644	edit dl rm
README.gnupg	1848	0644	edit dl rm
README.gnupg-sc	2354	0644	edit dl rm
README.keyctl	3583	0644	edit dl rm
README.md.gz	2223	0644	edit dl rm
README.opensc.gz	2219	0644	edit dl rm
v1.0.7-ReleaseNotes	2921	0644	edit dl rm
v1.1.0-ReleaseNotes.gz	2275	0644	edit dl rm
v1.1.1-ReleaseNotes	1796	0644	edit dl rm
v1.1.2-ReleaseNotes	1594	0644	edit dl rm
v1.1.3-ReleaseNotes	482	0644	edit dl rm
v1.2.0-ReleaseNotes.gz	2124	0644	edit dl rm
v1.3.0-ReleaseNotes.gz	2134	0644	edit dl rm
v1.3.1-ReleaseNotes	421	0644	edit dl rm
v1.4.0-ReleaseNotes.gz	2253	0644	edit dl rm
v1.4.1-ReleaseNotes	889	0644	edit dl rm
v1.4.2-ReleaseNotes	1630	0644	edit dl rm
v1.4.3-ReleaseNotes	2359	0644	edit dl rm
v1.5.0-ReleaseNotes.gz	3320	0644	edit dl rm
v1.5.1-ReleaseNotes	1295	0644	edit dl rm
v1.6.0-ReleaseNotes.gz	3818	0644	edit dl rm
v1.6.1-ReleaseNotes	1041	0644	edit dl rm
v1.6.2-ReleaseNotes	985	0644	edit dl rm
v1.6.3-ReleaseNotes	1859	0644	edit dl rm
v1.6.4-ReleaseNotes	2036	0644	edit dl rm
v1.6.5-ReleaseNotes	2479	0644	edit dl rm
v1.6.6-ReleaseNotes	1093	0644	edit dl rm
v1.6.7-ReleaseNotes	3333	0644	edit dl rm
v1.6.8-ReleaseNotes	2061	0644	edit dl rm
v1.7.0-ReleaseNotes	3101	0644	edit dl rm
v1.7.1-ReleaseNotes	1371	0644	edit dl rm
v1.7.2-ReleaseNotes	1487	0644	edit dl rm
v1.7.3-ReleaseNotes	811	0644	edit dl rm
v1.7.4-ReleaseNotes	657	0644	edit dl rm
v1.7.5-ReleaseNotes	833	0644	edit dl rm
v2.0.0-ReleaseNotes.gz	9728	0644	edit dl rm
v2.0.1-ReleaseNotes.gz	2226	0644	edit dl rm
v2.0.2-ReleaseNotes.gz	1992	0644	edit dl rm
v2.0.3-ReleaseNotes.gz	2448	0644	edit dl rm
v2.0.4-ReleaseNotes.gz	2325	0644	edit dl rm
v2.0.5-ReleaseNotes.gz	2068	0644	edit dl rm
v2.0.6-ReleaseNotes.gz	1960	0644	edit dl rm
v2.1.0-ReleaseNotes.gz	3484	0644	edit dl rm
v2.2.0-ReleaseNotes.gz	4582	0644	edit dl rm
v2.2.1-ReleaseNotes	1413	0644	edit dl rm
v2.2.2-ReleaseNotes	2151	0644	edit dl rm
v2.3.0-ReleaseNotes.gz	3250	0644	edit dl rm
v2.3.1-ReleaseNotes	1770	0644	edit dl rm
v2.3.2-ReleaseNotes	1499	0644	edit dl rm
v2.3.3-ReleaseNotes	1396	0644	edit dl rm
v2.3.4-ReleaseNotes.gz	2001	0644	edit dl rm
v2.3.5-ReleaseNotes.gz	3129	0644	edit dl rm
v2.3.6-ReleaseNotes	2316	0644	edit dl rm
v2.4.0-ReleaseNotes.gz	4766	0644	edit dl rm
v2.4.1-ReleaseNotes	1942	0644	edit dl rm
v2.4.2-ReleaseNotes	1375	0644	edit dl rm
v2.4.3-ReleaseNotes.gz	1996	0644	edit dl rm

Edit: /usr/share/doc/cryptsetup/v2.3.1-ReleaseNotes (1770B)

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.

cmd: