From: Milan Broz <mbroz@redhat.com>
To: korn-gmail@chardonnay.math.bme.hu
Cc: dm-crypt@saout.de, "András Korn" <korn.andras@gmail.com>
Subject: Re: [dm-crypt] solved: Re: How to recover partially overwritten LUKS volume?
Date: Mon, 27 Aug 2012 12:20:28 +0200 [thread overview]
Message-ID: <503B49EC.8050103@redhat.com> (raw)
In-Reply-To: <CAKUckQJkUc56MR=VKK4Gd+c+BjEJbtnz=J=Uwm+++vC8_MS2yQ@mail.gmail.com>
On 08/27/2012 11:51 AM, András Korn wrote:
> That means that the offsets from the FAQ don't apply to my LUKS
> container and that keyslot #2 has been wiped after all.
Not sure if it is good idea to have these in FAQ, it depends on
key size. (But there are usually only 3 variants for 128,256 and 512bits).
I wonder adding this directly to luksDump would help?
Like
...
Key material offset: 8
Key slot area offset: 0x1000 - 0x21000
...
(here with padding, perhaps it is better print used area only without padding...)
Milan
p.s.
very nice description of successful recovery, congrats :)
next prev parent reply other threads:[~2012-08-27 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 9:51 [dm-crypt] solved: Re: How to recover partially overwritten LUKS volume? András Korn
2012-08-27 10:06 ` Arno Wagner
2012-08-27 10:20 ` Milan Broz [this message]
2012-08-27 11:45 ` 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=503B49EC.8050103@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=korn-gmail@chardonnay.math.bme.hu \
--cc=korn.andras@gmail.com \
/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.