cryptsetup.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Ondrej Kozina <okozina@redhat.com>
To: cryptsetup@lists.linux.dev
Cc: xndr <xanda@gmx.co.uk>
Subject: Re: How to resume decryption on LUKS1 in-place
Date: Mon, 4 Mar 2024 16:45:21 +0100	[thread overview]
Message-ID: <6caca783-5a30-434c-b9f1-234a1bff9310@redhat.com> (raw)
In-Reply-To: <76ca5ef4-5298-4c03-bdc1-8b1ce012c7b4@gmx.co.uk>

On 04/03/2024 15:51, xndr wrote:
> For the record:-
> 
>       $: cryptsetup -V
>       cryptsetup 2.6.1 flags: UDEV BLKID KEYRING KERNEL_CAPI
> 
>       $: apt show cryptsetup
>       Package: cryptsetup
>       Version: 2:2.6.1-4~deb12u2
> 
> We see the latest stable version on GitLab is now 2.7.0; is it still
> recommended to rollback to 2.4.3?

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.

You'd need the old version only for this particular case. Nothing else.

Anyway, I'll send patch to upstream soon so there will be a proper fix 
for 2.7.0 and later releases.

Kind regards
O.


  reply	other threads:[~2024-03-04 15:45 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 [this message]
2024-03-04 16:34           ` xndr
2024-03-07 12:14             ` Ondrej Kozina
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=6caca783-5a30-434c-b9f1-234a1bff9310@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).