From: Milan Broz <gmazyland@gmail.com>
To: cryptsetup development <cryptsetup@lists.linux.dev>
Subject: [ANNOUNCE] cryptsetup 2.8.4
Date: Tue, 27 Jan 2026 15:51:52 +0100 [thread overview]
Message-ID: <406bc19f-0d9a-489e-914c-5dfa6a3a72dc@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1213 bytes --]
The cryptsetup 2.8.4 stable release is available at
https://gitlab.com/cryptsetup/cryptsetup
Please note that release packages are located on kernel.org
https://www.kernel.org/pub/linux/utils/cryptsetup/v2.8/
Feedback and bug reports are welcomed (please us project page issue tracker).
Cryptsetup 2.8.4 Release Notes
==============================
Stable bug-fix release.
All users of cryptsetup 2.8.x must upgrade to this version.
Changes since version 2.8.3
~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Fix integritysetup resize (grow) of the device if integrity bitmap mode is used.
Increasing the integrity device in bitmap mode did not work as integritysetup
incorrectly used journal settings that were not applicable.
* Fix device size status reports in cryptsetup and integritysetup.
If the device uses a sector size larger than 512 bytes, the newly reported byte
sizes (introduced in 2.8.0) in the status report were incorrectly displayed.
* BITLK: Fix unlocking BitLocker device with recovery passphrase.
If the recovery passphrase was present in the first keyslot, the device failed
to unlock. This bug was introduced in 2.8.2 with Clear Key support.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4753 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-01-27 14:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=406bc19f-0d9a-489e-914c-5dfa6a3a72dc@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox