From: Milan Broz <mbroz@redhat.com>
To: anton ivanov <run.into.flowers@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] [PATCH] When reading no single byte for the key abort.
Date: Tue, 29 Sep 2009 12:23:43 +0200 [thread overview]
Message-ID: <4AC1E02F.6030502@redhat.com> (raw)
In-Reply-To: <49a25c1e0909290303t5f220e32na7ec13d1d4b784ce@mail.gmail.com>
anton ivanov wrote:
> what are you talking about? I tried with empty file as passphrase,
> surely not working :)
I didn't say that empty keyfile can be used as real passphrase (in luksFormat),
but the verification (luksOpen) will fail with "No key available with this passphrase"
and with the patch it fails with different error - error during reading key.
I can imagine that some scripts can depend on this behaviour and
there is no real need to change it.
When you enter empty string from terminal, it does the same.
Milan
prev parent reply other threads:[~2009-09-29 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 7:21 [dm-crypt] [PATCH] When reading no single byte for the key abort Ludwig Nussel
2009-09-28 18:51 ` Milan Broz
2009-09-29 9:25 ` Ludwig Nussel
2009-09-29 10:03 ` anton ivanov
2009-09-29 10:04 ` anton ivanov
2009-09-29 10:23 ` Milan Broz [this message]
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=4AC1E02F.6030502@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=run.into.flowers@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox