Re: LUKS Header crruption
Robert Nichols <[email protected]>
| Newsgroups | gmane.linux.kernel.device-mapper.dm-crypt |
|---|---|
| Message-ID | <[email protected]> |
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" <[email protected]>
> To: [email protected]
> 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
_______________________________________________
dm-crypt mailing list
[email protected]
https://www.saout.de/mailman/listinfo/dm-crypt