Re: A new container with an old header

Thank you Michael for your suggestions!
Particularly valuable for me is the ability to check the checksum of a fragment of a file (I did not know this before):
$ dd if=luks-container bs=1048576 count=100 | md5sum -b

Instead of `truncate -s 200M` I found a better solution for my use case:
`head -c 200M /dev/urandom >> my-container`
It creates "real data" instead of "sparse file" (whatever that means) and is supposedly more secure.
Then I used `cryptsetup resize` and later `resize2fs /dev/mapper/xxx` and everything looks fine now :)

Cheers!