cryptsetup

Operating Systems

Cryptsetup and LUKS - open-source disk encryption

Latest v2.8.7 · by cryptsetupWebsite

Release activity

Release activity — 11 releases across 10 days in the last year. Each cell is one day; darker means more releases that day. Older weeks are hidden at this screen width.
MayJunJulAug
SundayNo releases on Apr 26, 2026No releases on May 3, 2026No releases on May 10, 2026No releases on May 17, 2026No releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 2026No releases on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026No releases on Aug 9, 2026
MondayNo releases on Apr 27, 2026No releases on May 4, 2026No releases on May 11, 2026No releases on May 18, 2026No releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 20261 release on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026No releases on Aug 10, 2026
TuesdayNo releases on Apr 28, 2026No releases on May 5, 2026No releases on May 12, 2026No releases on May 19, 2026No releases on May 26, 2026No releases on Jun 2, 2026No releases on Jun 9, 2026No releases on Jun 16, 2026No releases on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 20261 release on Jul 21, 2026No releases on Jul 28, 2026No releases on Aug 4, 2026No releases on Aug 11, 2026
WednesdayNo releases on Apr 29, 2026No releases on May 6, 2026No releases on May 13, 2026No releases on May 20, 2026No releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 2026No releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026No releases on Aug 12, 2026
ThursdayNo releases on Apr 30, 2026No releases on May 7, 2026No releases on May 14, 2026No releases on May 21, 2026No releases on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 2026No releases on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026No releases on Aug 13, 2026
FridayNo releases on May 1, 2026No releases on May 8, 2026No releases on May 15, 2026No releases on May 22, 2026No releases on May 29, 2026No releases on Jun 5, 2026No releases on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 20261 release on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 2026No releases on Jul 31, 2026No releases on Aug 7, 2026No releases on Aug 14, 2026
SaturdayNo releases on May 2, 2026No releases on May 9, 2026No releases on May 16, 2026No releases on May 23, 2026No releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026No releases on Aug 8, 2026No releases on Aug 15, 2026

11 releases in the last year, busiest day 2

Changelog

v2.8.7

LatestFrom commit messages

Version 2.8.7.

Added 4
  • Add keyring key type and load volume keys in intermediary keyring linked in thread keyring.
  • Support Aria and Camellia ciphers in libgcrypt backend.
  • Add storage wrappers option to use DMCRYPT wrapper only and add fallback to dmcrypt in LUKS21 keyslot processing.
  • integritysetup: support --integrity-legacy-hmac in open.
Changed 3
  • Remove logic for AF_ALG dependence in tcrypt and luks2, and do not print specific AF_ALG info in cryptsetup cipher benchmark.
  • Switch LUKS2 reencryption and convert code to more capable LUKS_check_cipher check.
  • Allow cached volume key in activation with CRYPT_KC_TYPE_KEY only and ensure CRYPT_VOLUME_KEY_NO_SEGMENT flag always creates unbound keyslot.
Fixed 3
  • Fix tcrypt, luks2, and OpenSSL backend security issues including safe allocation for password pool, length overflow checks, buffer size validation, HMAC return value checks, PBKDF2 cast overflow, and json keyslot leak on error path.
  • Fix reencryption name helper check and improve LUKS_check_cipher validation.
  • Fix integrity shift overflow test and --tries option use.
View originalPermalink
How v2.8.7 went

v2.8.5

From commit messages

Version 2.8.5.

Added 1
  • Support for external tokens without dlvsym in musl and argp detection with argp-standalone static-only library.
Changed 2
  • Use portable bitops.h instead of Linux endian.h in utf8.c and increased number of allowed threads in OpenSSL backend.
  • Meson build system improvements including UUID header path detection, pkg-config for popt library discovery, and crypto backend library dependency propagation to all targets.
Fixed 7
  • UUID verification of resumed devices now matches UUID stored in metadata.
  • Reading from wrong image offset, fvault2 metadata block offset check, and LUKS2 reencryption lock and data offset functions.
  • crypt_resize() data leak on error path, wiping of larger Veracrypt password pool, and crypt_capi_to_cipher() prefix validation.
  • Kernel crypto backend sa.salg_type snprintf check, OpenSSL CTX_dup failure handling, device_alignment for NULL device, and DM_INTEGRITY union access in _reload_device().
  • Keyring name buffer size in DM table with proper bounds checking, flags initialization to prevent reading uninitialized values on dm_flags() failure, and integrity sector size overflow from disk reads.
  • strtoll() failure checking, fvault2 key unwrapping memory allocation, OpenSSL RAND_bytes buffer size validation, and posix_fallocate error reporting.
  • Verity tree hash file flushing between levels and OpenSSL crypto backend build compatibility with LibreSSL.
View originalPermalink
How v2.8.5 went

v2.8.4

From commit messages

Version 2.8.4.

Fixed 4
  • Wrong device size status reports in cryptsetup and integritysetup.
  • bitlk no longer tries to use empty password for password keyslots.
  • integritysetup grow of bitmap protected devices.
  • gcc-16 warnings with fanalyzer.
View originalPermalink
How v2.8.4 went

v2.8.3

From commit messages

Version 2.8.3.

Fixed 1
  • BITLK FVE validation on big-endian platforms.
View originalPermalink
How v2.8.3 went

v2.8.2

From commit messages

Version 2.8.2.

Added 3
  • Support for PHMAC with integritysetup and cryptsetup.
  • Support for BitLocker clearkey.
  • Inline integrity flag set when no underlying dm-integrity device exists.
Fixed 7
  • BitLocker handling of NULL passwords and validation of FVE metadata.
  • OPAL sed-opal ioctl submission to R/W file descriptor and suppressed confusing debug messages.
  • Handling of too long label and subsystem fields.
  • LUKS2 device status in inline HW mode and detached header.
  • Possible use of uninitialized variable and inline format data device.
  • Typos in integritysetup man page and volume-key-file help.
  • Key-size descriptions and explicit mention of units (bytes) for volume key in header.
View originalPermalink
How v2.8.2 went

v2.8.1

From commit messages

Version 2.8.1.

Changed 3
  • Do not silently decrease PBKDF parallel cost (threads).
  • Weaken warning about /dev/urandom in man pages as recent kernels behave much better.
  • Documentation updates including clarification of --label, --sector-size, and --align-payload options, PBKDF hardcoded limits explanation, and removal of references to archeologic kernel versions.
Fixed 5
  • Fix bug in parsing of tcrypt device in crypt_init_by_name.
  • Fix unlocking BitLocker with multibyte UTF8 characters in passphrase.
  • Fix detecting status of chained modes in tcrypt.
  • Fix luks2-external-tokens-path option for meson and define EXTERNAL_LUKS2_TOKENS_PATH for autoconf.
  • Fix wrongly generated config.h paths and tmpfiles installation when $prefix is set.
View originalPermalink
How v2.8.1 went
View all

Discussion