From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS Header crruption
Date: Mon, 29 Jul 2019 08:56:21 -0500 [thread overview]
Message-ID: <qhmtu6$55ce$1@blaine.gmane.org> (raw)
In-Reply-To: <1853881426.34.1564402130365.JavaMail.gkos@xpska>
The key material is quite deliberately made just the opposite of redundant. It is artificially inflated (typically 4000X) to occupy a larger area of the disk, and in such a manner that successfully erasing any portion of that area makes the key unrecoverable.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
On 7/29/19 7:08 AM, Konstantin V. Gavrilenko wrote:
> Thanks Arno, thought so :(
> Its a real pity that metadata is not redundant in luks v1.
>
> Regards,
> Konstantin
>
>
>
> ----- Original Message -----
> From: "Arno Wagner" <arno@wagner.name>
> To: dm-crypt@saout.de
> Sent: Sunday, 28 July, 2019 11:00:49 PM
> Subject: Re: [dm-crypt] LUKS Header crruption
>
> Hi Konstantin,
>
> sorry, you data is gone. You overwrote the start of the first
> key-slot and there is no way to recover from that without backup.
>
> One of the reasons why I think RAID superblocks at the start of the
> device (and even more so at 4kB offset) are messed up and a sign
> of clueless designers.
>
> Regards,
> Arno
next prev parent reply other threads:[~2019-07-29 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1313728220.30.1564401565268.JavaMail.gkos@xpska>
2019-07-29 12:08 ` [dm-crypt] LUKS Header crruption Konstantin V. Gavrilenko
2019-07-29 13:56 ` Robert Nichols [this message]
2019-07-29 14:33 ` Milan Broz
[not found] <1590255742.9.1564314256863.JavaMail.gkos@xpska>
2019-07-28 11:57 ` Konstantin V. Gavrilenko
2019-07-28 21:00 ` Arno Wagner
2019-07-29 7:25 ` Uwe Menges
2019-07-29 9:28 ` 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='qhmtu6$55ce$1@blaine.gmane.org' \
--to=rnicholsnospam@comcast.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox