From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] No key available for this passphrase
Date: Tue, 29 Jan 2013 03:39:11 +0100 [thread overview]
Message-ID: <20130129023911.GA19313@tansi.org> (raw)
In-Reply-To: <CAFnMBaRDM8HXLi5f3E8sAr5kBSByPiC0uvyuX1wJQ9Mw-i2kmQ@mail.gmail.com>
On Mon, Jan 28, 2013 at 06:46:53PM -0500, .. ink .. wrote:
> [..]
>
> > but a function like this or any other
> > mechanism of header-protection would be nice to see as standard for LUKS.
> > Especially because the first keyslot is so likely to be corrupted by
> > partition
> > managers (should be aroud the offset of keyslot 0 where they start to dump
> > their
> > data?).
> >
> >
> has there been any study to find out which ones of the keyslots is most
> likely to get corrupted accidentally by various tools?
I do not think there is enough data. And there is the additional
problem that corruption in others than slot 0 will not be noticed
by most users. You are welcome to search the mai,ing-list archives
and generate a statistic, of course.
> will adding keys from the last slot going backwards add some protection
> from keys being inaccessible due to accidental header corruption by various
> tools?
I think most tools will kill the header. After that, damage to
key-slots does not matter much, as the header carries the all-iportant
salts. While it does happen occasionally that just a key-slot gets
corrupted, it is rare. The keyslot-checker I wrote was not due to
a dire need, but because I hacked together a version in Python that
read the disk directly in a 2-3 hours, and then Milan (rightfully)
asked me to do it right. Provided entertainment for me for a
weekend and an opportunity to look at libcryptsetup. I think we
may have seen someting like 5-6 cases altogether in the last few
years. No idea how many people managed to kill their LUKS containers,
but never reported it on the list.
And anyways, disks do die, so data-backup is mandatory even for
encrypted volumes. See the FAQ for some suggestions.
Arno
--
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
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2013-01-29 2:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 17:53 [dm-crypt] No key available for this passphrase Sebastian
2013-01-25 19:40 ` Arno Wagner
2013-01-25 19:57 ` Sebastian
2013-01-25 21:50 ` Arno Wagner
2013-01-26 10:15 ` Sebastian
2013-01-26 17:41 ` Arno Wagner
2013-01-27 8:42 ` Sebastian
2013-01-28 23:46 ` .. ink ..
2013-01-29 2:39 ` Arno Wagner [this message]
2013-01-31 13:43 ` Sebastian
2013-01-31 17:48 ` .. ink ..
-- strict thread matches above, loose matches on Subject: below --
2012-09-08 9:03 Marcos
2012-09-08 13:35 ` Arno Wagner
2012-09-08 18:47 ` Marcos
2012-09-08 20:02 ` Arno Wagner
2012-09-08 20:51 ` Marcos
2012-09-08 22:47 ` Arno Wagner
2012-09-09 12:53 ` Marcos
2012-09-09 13:49 ` Arno Wagner
2012-09-09 14:06 ` Marcos
2012-09-08 22:45 ` Matthias Schniedermeyer
2012-09-09 8:45 ` Milan Broz
2012-09-09 13:42 ` Arno Wagner
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=20130129023911.GA19313@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.