DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Cc: fabrice.bongartz@grenzecho.be
Subject: Re: [dm-crypt] luks passphrase stopped working after cryptsetup+libgcrypt update on arch linux
Date: Fri, 17 Jan 2014 12:14:35 +0100	[thread overview]
Message-ID: <52D9109B.2040906@gmail.com> (raw)
In-Reply-To: <1358734863.2409630.1389952114847.JavaMail.root@grenzecho.be>

On 01/17/2014 10:48 AM, Fabrice Bongartz wrote:
> Hi,
> 
> After upgrading cryptsetup from 1.6.3-1 to 1.6.3-2 and libgcrypt from
> 1.5.3-1 to 1.6.0-1 (those are the version number from the arch linux 
> package manager), I am unable to open my luks encrypted partitions
> using the corrent passphrase.
> 
> As can be seen here https://bbs.archlinux.org/viewtopic.php?id=175737
> I'm not the only Arch linux user who has encountered this problem.

Hi,
please use you distro bugzilla and once distro maintainer has enough info,
create upstream issue
Distro specific bug is https://bugs.archlinux.org/task/38550

I bet it is another problem in libgcrypt 1.6
(the first one is http://code.google.com/p/cryptsetup/issues/detail?id=199 where
I already sent fix directly to gcrypt upstream)

Please try to downgrade libgcrypt, rebuild cryptsetup 1.6.3 and try again.
(There is no whirlpool specific code in cryptsetup. I will check gcrypt
how gcrypt use whirlpool later though...)

I plan to release 1.6.4 soon with disabling slow pbkdf2 from gcrypt, so if there
is another issue it should be fixed as well.

Thanks,
Milan

p.s.
As upstream maintainer, I have really no time to fix distro specific issues
I personally use Debian/Gentoo/Fedora/CentoOS where I can do some distro specific things
but I cannot simply test everything. Distro maintainer understand distro details,
so he can send me all relevant debug logs etc.

Just one warning: if anyone said he tested "cryptsetup-nuke-keys (AUR) 1.6.3-2" or so
these report will go directly to /dev/null.
Please always use upstream code when reporting to upstream. Thanks.

  reply	other threads:[~2014-01-17 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <234831248.2409552.1389952059649.JavaMail.root@grenzecho.be>
2014-01-17  9:48 ` [dm-crypt] luks passphrase stopped working after cryptsetup+libgcrypt update on arch linux Fabrice Bongartz
2014-01-17 11:14   ` Milan Broz [this message]
2014-01-17 11:57     ` Fabrice Bongartz
2014-01-17 12:47       ` Milan Broz
2014-01-17  9:40 accounts

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=52D9109B.2040906@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=fabrice.bongartz@grenzecho.be \
    /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