From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com
 [IPv6:2a00:1450:4864:20::444])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 12 Sep 2018 06:44:45 +0200 (CEST)
Received: by mail-wr1-x444.google.com with SMTP id v17-v6so468211wrr.9
 for <dm-crypt@saout.de>; Tue, 11 Sep 2018 21:44:45 -0700 (PDT)
References: <3981e376-6bc1-eafa-661f-800527d1edd8@riseup.net>
 <0a634f10-a4fe-54e3-b6ad-edd3f7682ec3@redhat.com>
 <05d42a4b-7439-0f5a-21b0-d79d1195b07f@riseup.net>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <cdad2fc3-5013-0412-2634-3a11fe04a3bc@gmail.com>
Date: Wed, 12 Sep 2018 06:44:41 +0200
MIME-Version: 1.0
In-Reply-To: <05d42a4b-7439-0f5a-21b0-d79d1195b07f@riseup.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Troubleshooting: Header Conversion to argon2id
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: procmem <procmem@riseup.net>, Ondrej Kozina <okozina@redhat.com>, dm-crypt@saout.de
Cc: whonix-devel@whonix.org

On 12/09/18 06:16, procmem wrote:
> Ondrej Kozina:
>> On 09/11/2018 07:09 PM, procmem wrote:
>>> Hi, I went ahead and tested the commands recommended by Milan for
>>> converting headers to use the better pbkdf algo. Unfortunately I'm
>>> running into an obscure error and wanted your advice on how to solve it.
>>>
>>> Please see the output of the command with --debug
>>>
>> Hi,
>>
>> luksConvertKey command works only on LUKS2 keyslots. Looking at debug
>> output it seems your device is not LUKS2 type.
>>
>> Regards
>> Ondrej
> 
> Now that I think about it this can't be the reason because the header is
> LUKS2 when using cryptsetup 2.0 and above - which is the version
> included in Debian Testing/Buster.

No, header is not always LUKS2 by default, cryptsetup 2.0.x luksFormat still uses LUKS1
format by default. Do not mix version of utility and version of LUKS metadata format.

Anyway, it seems that there is no LUKS header on the device at all, or it is somehow
corrupted, all commands then must fail of course.

Can you please paste output of "blkid -p <device>" and "cryptsetup luksDump --debug <device>" ?

m.


> 
> Also running 'cryptsetup convert' with --debug gives the same error.
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> https://www.saout.de/mailman/listinfo/dm-crypt
>