From: protagonist <protagonist@depressiverobots.com>
To: Jindrich Kolman <kolman.jindrich@gmail.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors
Date: Fri, 24 Nov 2017 17:15:53 +0100 [thread overview]
Message-ID: <ba21e755-3d61-12e2-949c-4392bf4fe642@depressiverobots.com> (raw)
In-Reply-To: <CAMMcZ_r3rZWt6x58MCR4aoH8vAfoozhzjU23OeZsB=Gr24nTAg@mail.gmail.com>
Hello Jindrich,
could you get in direct contact with me and send some further technical
information regarding the affected drive / partition info / filesystem /
SMART values / .. ?
I'd be happy to help.
protagonist
On 24.11.2017 12:57, Jindrich Kolman wrote:
> About a week back, i was suddenly unable to open my luks-encrypted partition. Mysteriously, a day later, it then worked again, but since two days ago, i an again locked out. Would you be willing to share your code, protagonist?
>
>
>>My current memcmp of the first 512 bytes therefore works just as well on
>>LVM as on ext4 and has managed to find a bit flip on a deliberately
>>corrupted key slot.
>
>>However, this is bad news for my ultimate target of recovering the
>>actual master key of the SSD in question, as it seems my previous
>>1-error checks have been unsuccessful, but valid.
>>Regards,
>>protagonist
next prev parent reply other threads:[~2017-11-24 16:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 11:57 [dm-crypt] LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors Jindrich Kolman
2017-11-24 16:15 ` protagonist [this message]
[not found] <a6e54426-5188-d4c7-ee7b-6f022b84bf22@depressiverobots.com>
2017-04-21 14:26 ` [dm-crypt] LUKS header recovery attempt from apparently healthy SSD protagonist
2017-04-22 0:25 ` Arno Wagner
2017-04-22 13:33 ` Robert Nichols
2017-04-22 13:45 ` Arno Wagner
2017-04-22 18:02 ` [dm-crypt] LUKS header recovery attempt, bruteforce detection of bit errors protagonist
2017-04-23 20:03 ` [dm-crypt] LUKS header recovery attempt, bruteforce detection of AF-keyslot " protagonist
2017-04-24 5:50 ` Dominic Raferd
2017-04-24 13:26 ` protagonist
2017-04-24 17:00 ` Dominic Raferd
2017-04-24 17:44 ` Michael Kjörling
2017-04-24 23:49 ` protagonist
2017-04-25 13:14 ` Robert Nichols
2017-04-25 13:44 ` Dominic Raferd
2017-04-25 14:37 ` Robert Nichols
2017-04-25 14:43 ` Robert Nichols
2017-04-25 14:45 ` Ondrej Kozina
2017-04-25 16:16 ` Sven Eschenberg
2017-04-25 16:30 ` Milan Broz
2017-04-25 17:09 ` Sven Eschenberg
2017-04-26 14:45 ` Hendrik Brueckner
2017-04-26 18:46 ` Milan Broz
2017-04-28 15:51 ` protagonist
2017-04-30 15:06 ` protagonist
2017-04-30 18:39 ` 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=ba21e755-3d61-12e2-949c-4392bf4fe642@depressiverobots.com \
--to=protagonist@depressiverobots.com \
--cc=dm-crypt@saout.de \
--cc=kolman.jindrich@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.