From: Milan Broz <gmazyland@gmail.com>
To: Louis <spalax@gresille.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Option "validate passphrase" for command cryptsetup
Date: Tue, 19 Jun 2012 13:26:22 +0200 [thread overview]
Message-ID: <4FE061DE.5080200@gmail.com> (raw)
In-Reply-To: <4FE05A32.9010402@gresille.org>
On 06/19/2012 12:53 PM, Louis wrote:
> Hello,
> for information, I wrote a small C program to check if the given
> passphrase is correct, without doing anything on the disk. The command
> is used this way:
> If you think it can benefit cryptsetup, I offer to write the necessary
> patch to include it to cryptsetup (as a "luksValidateKey" LUKS action).
Special program or command is IMHO overkill, isn't enough just to add option
to cryptsetup luksOpen (--dry-run, --no-activate, whatever you prefer)?
So it will work just like
# cryptsetup luksOpen /dev/sdc anything --dry-run --verbose
Enter passphrase for /dev/sdc:
No key available with this passphrase.
Enter passphrase for /dev/sdc:
Key slot 0 unlocked.
Command successful.
Trivial to add to code... (while I am doing another RC today, it can be done
today even ;-)
Milan
next prev parent reply other threads:[~2012-06-19 11:26 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 [this message]
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
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=4FE061DE.5080200@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=spalax@gresille.org \
/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.