From: Milan Broz <mbroz@redhat.com>
To: Andreas <andreas@maxxle.de>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Problem opening device: PBKDF2_HMAC_SHA1: Assertion `iterations != 0' failed
Date: Sun, 02 May 2010 11:55:52 +0200 [thread overview]
Message-ID: <4BDD4C28.7020005@redhat.com> (raw)
In-Reply-To: <1272792218.20273.9.camel@legolas>
On 05/02/2010 11:23 AM, Andreas wrote:
> What i've done:
> ===============
> - Removed the device from the Ubuntu-box (it worked there perfectly)
> - Attached the device to the Knoppix-Box
> - Tried to open the device on the Knoppix-Box
> - Received an error (0.99.1 to 0.99)??
Hm. I almost sure you are hitting the same automatic conversion bug.
(~ only for disk formatted somewhere in version 1.0.3)
I removed that code from recent cryptsetup completely, it need different approach.
But this bug is very rare.
see http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/4060
If so, luckily it can be easily fixed. If you send me first 4kB
(visible LUKS header) I can fix it for you. (This part doesn't contain keyslots.)
dd if=/dev/≤your_luks_device> of=/backup.img bs=512 count=8
If you agree, please send me the header - backup.img - in private mail,
(optionally encrypted using my gpg key, id is 0xBB21822F on keyservers)
I'll send you back the fixed header (if it is this problem...)
I need anyway more examples of bad header to prepare some "fix" in new code
or at least add some FAQ entry.
Milan
prev parent reply other threads:[~2010-05-02 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 9:23 [dm-crypt] Problem opening device: PBKDF2_HMAC_SHA1: Assertion `iterations != 0' failed Andreas
2010-05-02 9:55 ` Milan Broz [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=4BDD4C28.7020005@redhat.com \
--to=mbroz@redhat.com \
--cc=andreas@maxxle.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox