From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJwKtZWcWUsK for ; Tue, 19 Jun 2012 15:41:32 +0200 (CEST) Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Tue, 19 Jun 2012 15:41:32 +0200 (CEST) Received: by werf13 with SMTP id f13so4132418wer.37 for ; Tue, 19 Jun 2012 06:41:32 -0700 (PDT) Message-ID: <4FE08189.2020106@gmail.com> Date: Tue, 19 Jun 2012 15:41:29 +0200 From: Milan Broz MIME-Version: 1.0 References: <4FE05A32.9010402@gresille.org> <4FE061DE.5080200@gmail.com> <20120619122915.GA1317@tansi.org> In-Reply-To: <20120619122915.GA1317@tansi.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Option "validate passphrase" for command cryptsetup List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt On 06/19/2012 02:29 PM, Arno Wagner wrote: > I think having this functionality is a good idea. >> Trivial to add to code... (while I am doing another RC today, it can be done >> today even ;-) Added --without activation option for luksOpen http://code.google.com/p/cryptsetup/source/detail?r=a38fcafcff9ae75feda12bc84d04b2cdaa591f9f# # cryptsetup luksOpen /dev/sdc x --without-activation -T 1 ; echo $? Enter passphrase for /dev/sdc: (good passphrase) 0 # cryptsetup luksOpen /dev/sdc x --without-activation -T 1 ; echo $? Enter passphrase for /dev/sdc: (bad passphrase) No key available with this passphrase. 2 Milan