From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] detached LUKS header size
Date: Sat, 23 Nov 2019 09:21:06 +0100 [thread overview]
Message-ID: <20191123082106.GA5984@tansi.org> (raw)
In-Reply-To: <62fc7ef6-e289-b268-17d5-6ac1df2f3904@gmx.ch>
If you do that, you kill the security model of LUKS.
The anti-forensic stripes are not some gadget, they
are central. Also, the key-slots are the stripes. There
are no 4kB you can take out and reconstruct the key
from them.
That said, I think if you have an issue with 10MB extra
today and are willing to sacrifice security to get rid
of them, then you are doing it massively wrong. Maybe
just do without encryption and security, it clearly is
not your first priority....
Regards,
Arno
On Sat, Nov 23, 2019 at 06:43:56 CET, Fourhundred Thecat wrote:
> Hello,
>
> I am using full-disk encryption with detached LUKS header.
>
> The LUKS header file itself is stored on an initrd image which I boot
> from USB, and then I decrypt the cryptsetup partition on my disk and
> chroot into it.
>
> The initrd system that I boot is very minimal, around 8MB in size.
>
> The LUKS image, being 2MB, is making the initrd image needlessly bigger.
>
> And the new LUKS2 format seems to use even larger header (10MB ?)
>
> >From what I understand, the keyslots themselves only use up 4KB of
> space, and the rest is used for "antiforensic stripes".
>
> This is probably a good idea when LUKS header is stored on disk together
> with the cryptsetup partition.
>
> But when using detached header, which is never stored on disk, this
> makes less sense
>
> Thus my question:
>
> is it possible, somehow, to reduce the size of the LUKS header to
> absolute minimum (4KB ?), when I don't need the antiforensic stripes ?
>
> thank you,
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> https://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
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
next prev parent reply other threads:[~2019-11-23 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 5:43 [dm-crypt] detached LUKS header size Fourhundred Thecat
2019-11-23 8:21 ` Arno Wagner [this message]
2019-11-24 6:34 ` Fourhundred Thecat
2019-11-24 8:16 ` Arno Wagner
2019-11-24 8:39 ` Milan Broz
2019-11-23 8:48 ` Milan Broz
2019-11-25 4:34 ` Fourhundred Thecat
2019-11-25 13:55 ` Milan Broz
2019-11-25 15:17 ` Fourhundred Thecat
2019-11-25 15:27 ` Milan Broz
2019-11-24 11:46 ` Michael Kjörling
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=20191123082106.GA5984@tansi.org \
--to=arno@wagner.name \
--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