All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Joe Hillenbrand <joehillen@gmail.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] luksAddKey hangs for ~85 minutes and then fails
Date: Tue, 21 Jun 2016 05:24:38 +0200	[thread overview]
Message-ID: <b3ccfeaf-d151-7a01-3e5d-95adf404d9c5@gmail.com> (raw)
In-Reply-To: <CANJQ5C5b6kEZ1JYwbjc9tAkWiZ6Y0cJ0Je9kR-TkA7nBQg6ZjA@mail.gmail.com>


On 06/21/2016 12:15 AM, Joe Hillenbrand wrote:
> I've been trying and trying to add a new key to one of my devices so
> that I can automount,
> but it consistently fails.
> 
> I run the following command. It hangs for ~85 minutes every time (I've
> tried at least 5 times)

Does it work if you just open the device? For example try

cryptsetup luksOpen /dev/md1 --test-passphrase

> and then fails with the "Not compatible PBKDF2 options" message and exit code 1.
> 
>     $ sudo cryptsetup luksAddKey /dev/md1 /etc/.md1.key
>     Enter any existing passphrase:
>     Not compatible PBKDF2 options (using hash algorithm sha256).

Could you please send output with added --debug switch?

It is failing PBKDF2 benchmark here so please try and send output
of these commands as well:

cryptsetup benchmark -h sha256 --debug
cryptsetup benchmark -h sha1 --debug

What distro and version it is?
Do you compile anything (kernel, cryptsetup, library...) yourself?

> I've tried generating several different keys of different sizes.
> Exact same behavior for all of them.

Key format is not the problem here.

Milan

  reply	other threads:[~2016-06-21  3:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 22:15 [dm-crypt] luksAddKey hangs for ~85 minutes and then fails Joe Hillenbrand
2016-06-21  3:24 ` Milan Broz [this message]
2016-06-21 15:51   ` Joe Hillenbrand
2016-06-22  7:28     ` Milan Broz
2016-06-22  7:39       ` Joe Hillenbrand
2016-06-23  6:29     ` Milan Broz
2016-07-06 23:50       ` Joe Hillenbrand

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=b3ccfeaf-d151-7a01-3e5d-95adf404d9c5@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=joehillen@gmail.com \
    /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.