From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Offset/size issue during LUKS recovery.
Date: Fri, 15 Jul 2016 11:13:51 +0200 [thread overview]
Message-ID: <20160715091351.GA28512@tansi.org> (raw)
In-Reply-To: <OFFAB11604.0F81952D-ON00257FF1.0004CDA4-00257FF1.0004D0B3@notes.na.collabserv.com>
On Fri, Jul 15, 2016 at 02:52:35 CEST, Julio Cesar Faracco wrote:
> Hi,
>
> Since I moved to the version 1.6.7 of cryptsetup, I started to have some problems to recovery a LUKS partition
> using a LUKS header file and a valid passphrase.
>
> # cryptsetup luksDump my_header_file --debug
> # Detected kernel Linux 3.10.0-327.13.1.el7.x86_64 x86_64.
> # Reading LUKS header of size 1024 from device /tmp/my_header_file
> # Key length 64, device size 8192 sectors, header size 4036 sectors.
[...]
> # # cryptsetup luksOpen /dev/loop0 my_enc_partition <<EOF
> $(PASSWORD)
> EOF
> # Detected kernel Linux 3.10.0-327.13.1.el7.x86_64 x86_64.
> # Reading LUKS header of size 1024 from device /tmp/my_header_file
> # Key length 64, device size 4060 sectors, header size 4036 sectors.
I take it, the device is 8192 sectors, i.e. 4MB?
If so, there seem to be a bug in device-size detection
as used by luksOpen.
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2016-07-15 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 0:52 [dm-crypt] Offset/size issue during LUKS recovery Julio Cesar Faracco
2016-07-15 7:33 ` Milan Broz
2016-07-15 9:13 ` Arno Wagner [this message]
2016-07-15 11:12 ` Milan Broz
2016-07-15 13:13 ` Arno Wagner
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=20160715091351.GA28512@tansi.org \
--to=arno@wagner.name \
--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.