All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miklos Bagi <miklos.bagi@mbjr.hu>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Is partial LUKS recovery possible?
Date: Thu, 02 Dec 2010 13:15:52 +0100	[thread overview]
Message-ID: <4CF78DF8.1000102@mbjr.hu> (raw)
In-Reply-To: <4CF774C3.2020904@mbjr.hu>

Apologies for replying my own post.

I believe I found the not so happy answer for me in Dr. Wagner's monthly
FAQ.

Is it possible to provide salt manually?
Implementing a simple logic may allow re-generating the original header
in case something bad happens, but I admit it makes sense keeping
backups of lhdrs somewhere safe.

Thanks,
Miklos

On 12/02/2010 11:28 AM, Miklos Bagi wrote:
> Hi all,
>
> I'm hoping to get directions with a 'small' recovery task.
>
> Given a partition that's known to be a broken LUKS one, lhdr is missing
> (incl magic, chipher, hash, uuid, etc.), however there are some facts known:
> - chipher: aes-cbc-essiv:sha256
> - keysize: 256 bits
> - offset: 2056 sectors
> - most importantly: we have the master key file available.
>
> I have the suspicion that the first approx 10% of the partition have
> been overwritten with random data.
> What are the chances of recovering any data in the given scenario?
>
> Thanks in advance,
> mB
>

  reply	other threads:[~2010-12-02 12:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 10:28 [dm-crypt] Is partial LUKS recovery possible? Miklos Bagi
2010-12-02 12:15 ` Miklos Bagi [this message]
2010-12-02 17:39   ` Arno Wagner
2010-12-02 17:44     ` Nargis Khan
2010-12-02 12:31 ` Mario 'BitKoenig' Holbe
2010-12-02 14:17   ` Miklos Bagi
2010-12-02 15:45     ` Mario 'BitKoenig' Holbe
2010-12-02 16:20       ` Milan Broz
2010-12-02 16:28         ` Mario 'BitKoenig' Holbe
2010-12-02 17:04           ` Milan Broz
2010-12-02 17:11             ` Mario 'BitKoenig' Holbe
     [not found]       ` <4CF81339.9070004@mbjr.hu>
2010-12-02 22:27         ` Mario 'BitKoenig' Holbe

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=4CF78DF8.1000102@mbjr.hu \
    --to=miklos.bagi@mbjr.hu \
    --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.