From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS header size
Date: Tue, 3 Aug 2010 13:18:39 +0200 [thread overview]
Message-ID: <20100803111839.GA9916@tansi.org> (raw)
In-Reply-To: <AANLkTi=6RytcDRKMUtvajjjT3z9TB_u6QTSS1Xo7dV0U@mail.gmail.com>
Look into the FAQ under "What does the on-disk structure of LUKS look
like?"
Arno
On Tue, Aug 03, 2010 at 04:41:33PM +0600, Alexander Konovalenko wrote:
> On Mon, Aug 2, 2010 at 05:01, Arno Wagner <arno@wagner.name> wrote:
> >
> > sorry, but you will have wiped the salt in the header, which
> > makes recovery impossible. You will also have wiped all keys
> > (they take about the first 8.5MB), which again does make recovery
> > impossible. In fact, any recovery from this would mean that
> > LUKS is badly broken security-wise.
>
> 8.5 MB? I thought a LUKS header usually takes only 2056 512-byte
> sectors, which is slightly more than 1 MiB. I wonder where does that
> belief come from. Almost all LUKS partitions I've been dealing with
> have been created by Ubuntu's debian-installer. So debian-installer's
> default must be the culprit.
>
> What's the recommended LUKS header size?
>
> -- Alexander
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2010-08-03 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 10:41 [dm-crypt] LUKS header size Alexander Konovalenko
2010-08-03 11:02 ` Milan Broz
2010-08-03 11:18 ` Arno Wagner [this message]
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=20100803111839.GA9916@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.