From: Jonas Meurer <jonas@freesources.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Option "validate passphrase" for command cryptsetup
Date: Tue, 19 Jun 2012 18:46:18 +0200 [thread overview]
Message-ID: <4FE0ACDA.8040302@freesources.org> (raw)
In-Reply-To: <4FE0A548.7030007@gmail.com>
Hey Milan,
Am 19.06.2012 18:14, schrieb Milan Broz:
> On 06/19/2012 05:04 PM, jonas wrote:
>
>> if I'm not wrong, one difference between Louis' suggestion and the way
>> you implemented it is, that the former works with active devices, and
>> the latter doesn't, right?
>
> No, it is exactly the same. It works even for active devices.
> (Check for active device is later.)
great to hear that I was wrong ;)
>> I like the idea of a --dry-run option which works for all commands,
>> just like a simulation mode. But as well I like the idea of a command
>> for key validation, which takes the same commandline options as
>> luksOpen, and simply verifies whether the given key (passphrase,
>> keyfile, whatever) is valid.
>
> Well, universal --dry-run is nice idea but I am not going to implement it now.
> (and I would perhaps do it differently - do everything as is except final
> on-disk metadata update or in-kernel device change.)
Now that my concerns above are proved wrong I don't consider support for
global --dry-run option that important anymore.
> Well, I have local commit renaming this luksOpen option to --test-passphrase.
> If there are no other suggestions for today, I'll commit it.
>
> Milan
> (grumbling something about bikeshedding :-)
To make it even worse: I don't consider --test-passphrase a good name
for the option. But I don't care that much about names either.
Regards,
jonas
next prev parent reply other threads:[~2012-06-19 16:46 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
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 [this message]
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=4FE0ACDA.8040302@freesources.org \
--to=jonas@freesources.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.