From: Fabrice Bongartz <fabrice.bongartz@grenzecho.be>
To: dm-crypt@saout.de
Subject: [dm-crypt] luks passphrase stopped working after cryptsetup+libgcrypt update on arch linux
Date: Fri, 17 Jan 2014 10:48:34 +0100 (CET) [thread overview]
Message-ID: <1358734863.2409630.1389952114847.JavaMail.root@grenzecho.be> (raw)
In-Reply-To: <234831248.2409552.1389952059649.JavaMail.root@grenzecho.be>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
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.
Forum user "eisensheng" pointed out that it seems to be related to the whirlpool hash which I am also using:
"
Appears to be a problem with the whirlpool hash option.
I've created the following LUKS containers on an older system with
libgcrypt 1.5.3-1
cryptsetup 1.6.3-1
and tried to open those LUKS containers on an updated system with
libgcrypt 1.6.0-1
cryptsetup 1.6.3-2
# cryptsetup luksFormat /dev/sdj1 --hash whirlpool -c aes-cbc-plain -s 128
-> can't open
# cryptsetup luksFormat /dev/sdj1 --hash whirlpool -c serpent-xts-essiv:sha256 -s 128
-> can't open
# cryptsetup luksFormat /dev/sdj1 --hash sha1 -c serpent-xts-essiv:sha256 -s 128
-> can open
"
Cheers,
Fabrice Bongartz
[-- Attachment #2: Type: text/html, Size: 1371 bytes --]
next parent reply other threads:[~2014-01-17 10:00 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 ` Fabrice Bongartz [this message]
2014-01-17 11:14 ` [dm-crypt] luks passphrase stopped working after cryptsetup+libgcrypt update on arch linux Milan Broz
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=1358734863.2409630.1389952114847.JavaMail.root@grenzecho.be \
--to=fabrice.bongartz@grenzecho.be \
--cc=dm-crypt@saout.de \
/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.