From: Ondrej Kozina <okozina@redhat.com>
To: cryptsetup <cryptsetup@lists.linux.dev>
Cc: xndr <xanda@gmx.co.uk>
Subject: Re: How to resume decryption on LUKS1 in-place
Date: Thu, 7 Mar 2024 13:14:31 +0100 [thread overview]
Message-ID: <dce9e0d8-dbfa-4b1a-ab61-33b6c7bc770a@redhat.com> (raw)
In-Reply-To: <08281b96-b6c3-433e-83ae-3b6b382714ce@gmx.co.uk>
On 04/03/2024 17:34, xndr wrote:
>
>> In general? No I don't recommend to downgrade to 2.4.3 for normal
>> operation. It's just currently the best option to workaround the bug
>> introduced in 2.5.0 regarding resuming LUKS1 decryption operation.
>
> Apologies - my bad; this is really what we meant.
No problem, the issue is already fixed upstream[1]. Will be released
within cryptsetup 2.7.1.
[1]: https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/616
Kind regards
O.
next prev parent reply other threads:[~2024-03-07 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 17:22 How to resume decryption on LUKS1 in-place xndr
2024-02-22 11:04 ` Ondrej Kozina
2024-03-01 13:12 ` xndr
2024-03-04 10:59 ` Ondrej Kozina
2024-03-04 14:51 ` xndr
2024-03-04 15:45 ` Ondrej Kozina
2024-03-04 16:34 ` xndr
2024-03-07 12:14 ` Ondrej Kozina [this message]
2024-04-03 18:24 ` xndr
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=dce9e0d8-dbfa-4b1a-ab61-33b6c7bc770a@redhat.com \
--to=okozina@redhat.com \
--cc=cryptsetup@lists.linux.dev \
--cc=xanda@gmx.co.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).