From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Can't add a new key, "No key available with this passphrase".
Date: Sun, 05 Sep 2010 11:54:07 +0200 [thread overview]
Message-ID: <4C8368BF.2010808@redhat.com> (raw)
In-Reply-To: <20100904091240.GA22707@tansi.org>
On 09/04/2010 11:12 AM, Arno Wagner wrote:
> On Fri, Sep 03, 2010 at 03:39:00PM -0400, PsiStormYamato wrote:
>> Anyway, my point is that a simple modification of the wording of
>> cryptsetup's responses would help to prevent such a problem with future
>> newbies.
>
> I agree.
>
> @Milan: Do we have a wish-list process for things like this
> besides asking on the list?
Add issue to http://code.google.com/p/cryptsetup/issues/list
ideally with description what you think it should display instead.
Milan
prev parent reply other threads:[~2010-09-05 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 4:24 [dm-crypt] Can't add a new key, "No key available with this passphrase" PsiStormYamato
2010-09-03 7:30 ` Arno Wagner
2010-09-03 15:36 ` PsiStormYamato
2010-09-03 18:16 ` Arno Wagner
2010-09-03 18:46 ` Arno Wagner
[not found] ` <1283542740.2186.12.camel@shadowtek.localdomain>
2010-09-04 9:12 ` Arno Wagner
2010-09-05 9:54 ` Milan Broz [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=4C8368BF.2010808@redhat.com \
--to=mbroz@redhat.com \
--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