All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guilhem Moulin <guilhem@fripost.org>
To: Dominic Raferd <dominic@timedicer.co.uk>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk
Date: Fri, 7 Jun 2019 12:52:09 +0200	[thread overview]
Message-ID: <20190607105209.GA5716@fripost.org> (raw)
In-Reply-To: <CAF9Mo3+KwchO_e0YF9zr+v9=Gq1J_73ya0anvDYWVRxxDNuh8A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

Hi,

On Fri, 07 Jun 2019 at 09:56:52 +0100, Dominic Raferd wrote:
> On Wed, 29 May 2019 at 14:44, Guilhem Moulin <guilhem@fripost.org> wrote:
>> I guess that if you want to stick to decrypt_derived your options are
>> to use `luksFormat --type luks1` (or `convert --type luks1`);
> 
> unfortunately this doesn't work. I try it (booting from SystemRescueCD):
> 
> # cryptsetup convert /dev/sda5 --type luks1
> […] 
> Cannot convert to LUKS1 format - keyslot 0 is not LUKS1 compatible.

For LUKS1, the only supported PBKDF algorithm is PBKDF2 (while for LUKS2
it defaults to argon2i), you therefore need to remove existing
non-PBKDF2 keyslots with `cryptsetup luksKillSlot`, or convert them with
`cryptsetup luksConvertKey --pbkdf pbkdf2`.

Cheers,
-- 
Guilhem.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-06-07 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 11:41 [dm-crypt] LUKS + dm-crypt Debian/Ubuntu expanding encrypted root LV onto 2nd disk Dominic Raferd
2019-05-22 12:46 ` Arno Wagner
2019-05-22 12:53   ` Dominic Raferd
2019-05-22 13:15     ` Arno Wagner
2019-05-22 17:16     ` Guilhem Moulin
2019-05-29  9:56       ` Dominic Raferd
2019-05-29 11:06         ` Ondrej Kozina
2019-05-29 11:26           ` Dominic Raferd
2019-05-29 13:43             ` Guilhem Moulin
2019-06-07  8:56               ` Dominic Raferd
2019-06-07 10:52                 ` Guilhem Moulin [this message]

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=20190607105209.GA5716@fripost.org \
    --to=guilhem@fripost.org \
    --cc=dm-crypt@saout.de \
    --cc=dominic@timedicer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.