Second copy of LUKS header

[GoogleCodeExporter]

It would be really nice if cryptsetup could keep a second copy of the LUKS 
header at the END of the container.  Should probably be an optional thing but 
on by default.  One concern with this would be older versions of cryptsetup not 
updating the second copy when the first is changed - eg the key-slot you 
thought you flushed is still there.  Not sure what a good way to deal with that 
would be.

Original issue reported on code.google.com by ryan.cas...@gmail.com on 14 Aug 2010 at 12:38

[GoogleCodeExporter]

Oh, I see now that this is planned for LUKS2.  Silly me.

Original comment by ryan.cas...@gmail.com on 14 Aug 2010 at 12:44

[GoogleCodeExporter]

It would be nice to have a copy at the beginning of the disk also. There 
already is room for it (payload offset) and easy to make more room by upping 
the default offset. A new header format is not really required for this, and it 
would make LUKS resilient against single sector corruption cases such as these:

http://bpaste.net/show/NNT1xzo4VGeBqEAScBqh/ (line 3910)
http://paste.ubuntuusers.de/234850/
http://permalink.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/6455
...

(Something out there is zapping LUKS headers, not sure what.)

Original comment by Andreas....@gmail.com on 19 Aug 2014 at 5:54

[GoogleCodeExporter]

Issue 234 has been merged into this issue.

Original comment by gmazyl...@gmail.com on 6 Dec 2014 at 9:04

[GoogleCodeExporter]

Can someone please help me and decode the message below:
<div id='msgSandbox_AMbmjkQAAA2BNVJDX2FAAAADg13N4' class='msgSandbox' 
style='padding: 1.5em 0.5em 0.5em 1.2em; word-wrap: break-word;' ><BR><BR></div>
Thank you

Original comment by bwelsh4545@att.net on 17 Dec 2014 at 4:19