From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS Header crruption
Date: Mon, 29 Jul 2019 16:33:28 +0200 [thread overview]
Message-ID: <232d89f2-8c0f-0c08-1f93-dd3a3cf1a076@gmail.com> (raw)
In-Reply-To: <qhmtu6$55ce$1@blaine.gmane.org>
On 29/07/2019 15:56, Robert Nichols wrote:
> 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.
Exactly. And this part is not changed even in LUKS2
(only metadata is stored twice).
For LUKS2, we just store keyslots content in area with higher offset,
seems that data corruption (caused by overwriting by random too-clever
software) is not so common here (like for the keyslot 0 in LUKS1).
Solution is to backup LUKS header.
Milan
next prev parent reply other threads:[~2019-07-29 14:33 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
2019-07-29 14:33 ` Milan Broz [this message]
[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=232d89f2-8c0f-0c08-1f93-dd3a3cf1a076@gmail.com \
--to=gmazyland@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox