From: "Thomas Bächler" <thomas@archlinux.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Option "validate passphrase" for command cryptsetup
Date: Tue, 19 Jun 2012 15:54:29 +0200 [thread overview]
Message-ID: <4FE08495.8070706@archlinux.org> (raw)
In-Reply-To: <4FE08189.2020106@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
Am 19.06.2012 15:41, schrieb Milan Broz:
> 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
I find the option name --without-activation to be quite long and hard to
type. Is there any reason why you didn't choose '--dry-run' as you first
suggested?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2012-06-19 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 10:53 [dm-crypt] Option "validate passphrase" for command cryptsetup Louis
2012-06-19 11:26 ` Milan Broz
2012-06-19 12:29 ` Arno Wagner
2012-06-19 13:41 ` Milan Broz
2012-06-19 13:54 ` Thomas Bächler [this message]
2012-06-19 14:17 ` Milan Broz
2012-06-19 14:56 ` Matthias Schniedermeyer
2012-06-19 16:20 ` ken
2012-06-19 22:02 ` Heinz Diehl
2012-06-19 15:04 ` jonas
2012-06-19 16:14 ` Milan Broz
2012-06-19 16:46 ` Jonas Meurer
2012-06-20 1:13 ` Arno Wagner
2012-06-19 16:56 ` ken
2012-06-20 7:41 ` Louis
2012-06-20 8:27 ` Milan Broz
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=4FE08495.8070706@archlinux.org \
--to=thomas@archlinux.org \
--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.