From: Milan Broz <mbroz@redhat.com>
To: "Nico R." <n-roeser@gmx.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Problem with piped passphrases containing newline character
Date: Thu, 27 May 2010 11:20:39 +0200 [thread overview]
Message-ID: <4BFE3967.6030703@redhat.com> (raw)
In-Reply-To: <4BFDA544.1060707@gmx.net>
On 05/27/2010 12:48 AM, Nico R. wrote:
> It used to work properly with cryptsetup-1.0.6. However, I am now
> experiencing an error with cryptsetup-1.1.1 if the passphrase is
> containing a newline character. I am using a simplified testcase to show
> the problem. The following commands are written for bash. I assume that
> there is a block device named /dev/loop0 which has enough space to hold
> a LUKS container.
>
> $ export LC_ALL=POSIX
> $ echo -n $'foo\nbar' | sudo \
> cryptsetup luksFormat /dev/loop0 -
> $ echo -n $'foo\nbar' | sudo \
> cryptsetup --key-file=- luksOpen /dev/loop0 testing
> No key available with this passphrase.
Yes, seems there is regression.
Can you report this as new issue to project page? I'll close it when
it is fixed (and I'll add this test to regression tests to no repeat it again.)
Milan
next prev parent reply other threads:[~2010-05-27 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 22:48 [dm-crypt] Problem with piped passphrases containing newline character Nico R.
2010-05-27 9:20 ` Milan Broz [this message]
2010-05-28 8:34 ` Nico R.
2010-05-28 8:43 ` Milan Broz
2010-05-28 9:06 ` Nico R.
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=4BFE3967.6030703@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=n-roeser@gmx.net \
/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