Re: FAQ :WAS: LUKS2 on disk format

Arno Wagner <[email protected]>
Newsgroups gmane.linux.kernel.device-mapper.dm-crypt
Message-ID <[email protected]>
Hi JT,

thanks I had already planned to add this one.

Regards,
Arno

On Tue, May 12, 2020 at 01:15:27 CEST, JT wrote:
> I had a similar question on my list.  This would be a good one for the
> revised FAQ.
> 
> Q:  What is the size of the LUKS2 header?
> A:  the LUKS header size is configurable.  16MB is the default size. 
> It can be changed by .....
> 
> Q: Does all metadata exist in the header?  Can I be sure that there is
> no LUKS metadata somewhere in the middle or in the end of the drive?  
> A: Yes, all LUKS metadata is stored in the LUKS heaer.  (Most of the
> area is reserved for keyslots, used in online reencryption.)
> 
> There is a small exception if you use experimental integrity protection
> (authenticated encryption) where dm-crypt is stacked over dm-integrity
> device.  In that case there is a dm-integrity superblock at the
> beginning of data area which contains only configuration of dm-integrity metadata.  No LUKS metadata is stored in this location. The superblock is required by the kernel dm-integrity implementation.
> 
> 
> _______________________________________________
> dm-crypt mailing list
> [email protected]
> https://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: [email protected]
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier
_______________________________________________
dm-crypt mailing list
[email protected]
https://www.saout.de/mailman/listinfo/dm-crypt
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.