From: Matthias Schniedermeyer <ms@citd.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] No key available for this passphrase
Date: Sun, 9 Sep 2012 00:45:19 +0200 [thread overview]
Message-ID: <20120908224519.GA9926@citd.de> (raw)
In-Reply-To: <20120908200221.GB31299@tansi.org>
On 08.09.2012 22:02, Arno Wagner wrote:
>
> You can have up to 8 with LUKS. Each gets it own key-slot.
> Unfortunately, the key-slot with the highest risk to get
> damaged is the first one and that is where a single passphrase
> ends up in if you do not override the placement default.
If that happens so often, why not change the default and place the first
key in slot 8?
(Assuming that can be done without significant compatibility issues)
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2012-09-08 22:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 9:03 [dm-crypt] No key available for this passphrase 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 23:16 ` [dm-crypt] Re2: " Arno Wagner
2012-09-09 12:58 ` Marcos
2012-09-08 22:45 ` Matthias Schniedermeyer [this message]
2012-09-09 8:45 ` [dm-crypt] " Milan Broz
2012-09-09 13:42 ` Arno Wagner
-- strict thread matches above, loose matches on Subject: below --
2013-01-25 17:53 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
2013-01-31 13:43 ` Sebastian
2013-01-31 17:48 ` .. ink ..
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=20120908224519.GA9926@citd.de \
--to=ms@citd.de \
--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.