All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS encrypted hard disk crashed. Recovery question
Date: Fri, 19 Aug 2016 13:58:41 +0200	[thread overview]
Message-ID: <20160819115841.GA8705@tansi.org> (raw)
In-Reply-To: <830443834.15018837.1471607121907.JavaMail.yahoo@mail.yahoo.com>

Hi Saibal,

On Fri, Aug 19, 2016 at 13:45:21 CEST, Saibal Kumar Adhya wrote:
>    [saibal] Thanks a lot Michael.
>    > If you are able to somehow gain access to the key slots in the LUKS
>    > header, it should be possible to decrypt the (stored) payload data,
>    to
>    > the extent that the data recovery agency was able to recover the
>    data.
>    > What they were not able to recover will decrypt to nonsense.
> 
>    [saibal] I have couple of following question.
> 
>    1) Is there a way to know, if the key slot area in the LUKS header has
>    been recovered or not? How to recover the entire partition from there?

Try a LuksOpen. It does not care about filesystem damage, but it
will obnly work if header and keyslot are undamaged.

>    2) This question is for my information. As I understand, LUKS header
>    and "key-slot" are very very critical. So, if any of these sectors get
>    damaged then the entire partition is un-usable. Is there a backup copy
>    of LUKS header and key slots, kept within the partition itself?
>    Thanks in advance.

No. You have to do such a backup yourself. See most of FAQ Section 6:
https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions

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

      reply	other threads:[~2016-08-19 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874579112.14972576.1471597033535.JavaMail.yahoo.ref@mail.yahoo.com>
2016-08-19  8:57 ` [dm-crypt] LUKS encrypted hard disk crashed. Recovery question Saibal Kumar Adhya
2016-08-19  9:44   ` Michael Kjörling
2016-08-19 11:45   ` Saibal Kumar Adhya
2016-08-19 11:58     ` Arno Wagner [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=20160819115841.GA8705@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.