From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Restore a LUKS partition
Date: Thu, 21 Nov 2013 16:44:58 +0100 [thread overview]
Message-ID: <20131121154458.GA28782@tansi.org> (raw)
In-Reply-To: <528DC045.2040000@elso.mine.nu>
Ok, whatever happened, /dev/sda6 is not a LUKS device. There
is one hidden in there at offset 0x7e00 = 32256 though.
Looks like there was some LVM or other wrapper around it,
The crypsetup man page comments on this sutuation as follows:
"But note that when the LUKS header is at a nonzero offset
in a device, then the device is not a LUKS device
anymore, but has a LUKS container stored in it at an offset."
I am not sure how to access this. Maybe something like
losetup -o 32256 /dev/loop0 /dev/sda6
would work. If
cryptsetup -v isLuks /dev/loop0
woeks afterwards, than you might acces the container
this way. Also note that for LUKS you do not need
to specify cipher or hash (except when formating) as
they are stored in the LUKS header.
Arno
On Thu, Nov 21, 2013 at 09:11:49 CET, Michael Grosseck wrote:
> On 21.11.2013 02:57, Arno Wagner wrote:
> >hd /dev/sda6 | head
> thanks Arno for your reply, the command above gives me this output:
>
> 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> |................|
> *
> 000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ef
> |................|
> 000001c0 ff ff 83 ef ff ff 3f 00 00 00 11 31 9c 00 00 00
> |......?....1....|
> 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> |................|
> *
> 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
> |..............U.|
> 00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> |................|
> *
> 00007e00 4c 55 4b 53 ba be 00 01 62 6c 6f 77 66 69 73 68
> |LUKS....blowfish|
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-11-21 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 1:25 [dm-crypt] Restore a LUKS partition Michael Grosseck
2013-11-21 1:57 ` Arno Wagner
2013-11-21 8:11 ` Michael Grosseck
2013-11-21 15:44 ` Arno Wagner [this message]
2013-11-21 16:19 ` Robert Nichols
2013-11-21 21:53 ` Michael Grosseck
2013-11-21 22:36 ` Arno Wagner
2013-11-21 22:37 ` 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=20131121154458.GA28782@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.