From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (unknown [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Sun, 5 Sep 2010 11:54:13 +0200 (CEST) Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o859s79s009334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 5 Sep 2010 05:54:08 -0400 Received: from [10.36.8.116] (vpn2-8-116.ams2.redhat.com [10.36.8.116]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o859s6al021792 for ; Sun, 5 Sep 2010 05:54:07 -0400 Message-ID: <4C8368BF.2010808@redhat.com> Date: Sun, 05 Sep 2010 11:54:07 +0200 From: Milan Broz MIME-Version: 1.0 References: <1283487886.3576.31.camel@shadowtek.localdomain> <20100903073039.GB3410@tansi.org> <1283528215.4980.64.camel@shadowtek.localdomain> <20100903181646.GB11768@tansi.org> <1283542740.2186.12.camel@shadowtek.localdomain> <20100904091240.GA22707@tansi.org> In-Reply-To: <20100904091240.GA22707@tansi.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Can't add a new key, "No key available with this passphrase". List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de 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