All of lore.kernel.org
 help / color / mirror / Atom feed
From: verdi <vermail@fromru.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] mk-digest and mk-sault DAMAGE
Date: Tue, 29 Sep 2009 23:54:03 +0400	[thread overview]
Message-ID: <4AC265DB.6090500@fromru.com> (raw)

Hello everyone.

Something has damaged mk-digest and mk-salt info on my LUKS partition's
header... I DO know the LUKS-passphrase (which is used to decrypt the
master key which then decrypts the bulk-data) and according to luksDump
the Key slot 0 seem aslo be alive...

Is there any opportunity to retrieve the encrypted data from that
partition? You can see below that Key Slot 0 Salt seems to be normal,
but MK digest and MK salt is overwritten with zeros somewhere
somehow..................

LUKS header information for /dev/sda4
 
Version:        1
Cipher name:    blowfish
Cipher mode:    cbc-plain
Hash spec:      sha1
Payload offset: 3528
MK bits:        448
MK digest:      40 0b 00 00 00 00 24 01 00 00 00 00 00 00 00 00 00 00 00 00
MK salt:        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
                00 00 12 01 c3 00 80 00 9b 1e 81 be 4c 75 2a fb
MK iterations:  10
UUID:           74db9b4c-f4a4-49fa-8ef2-8b2d1df525eb
 
Key Slot 0: ENABLED
        Iterations:             215014
        Salt:                   68 b5 3a 6d a7 ec 96 18 1d 05 da 2f a5
4f 96 5e
                                3a fa 80 3b d5 20 cb 1b d3 63 dd c0 f2
18 38 0f
        Key material offset:    8
        AF stripes:             4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED

                 reply	other threads:[~2009-09-29 19:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AC265DB.6090500@fromru.com \
    --to=vermail@fromru.com \
    --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.