DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 28 May 2010 10:43:59 +0200	[thread overview]
Message-ID: <4BFF824F.8070607@redhat.com> (raw)
In-Reply-To: <4BFF801D.3060100@gmx.net>

On 05/28/2010 10:34 AM, Nico R. wrote:
> On 2010-05-27T09:20Z, Milan Broz wrote:
>> On 05/27/2010 12:48 AM, Nico R. wrote:
>>
> [issue with embedded newlines in passphrases]
>>
>> Yes, seems there is regression.
>>
>> Can you report this as new issue to project page?
> 
> As I don’t have a Google account, no. You’ll have to add the issue
> yourself or ask someone else to do that, sorry.

Well, ok. It should be fixed in current devel code anyway.

http://code.google.com/p/cryptsetup/source/detail?r=237

Milan

  reply	other threads:[~2010-05-28  8:44 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
2010-05-28  8:34   ` Nico R.
2010-05-28  8:43     ` Milan Broz [this message]
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=4BFF824F.8070607@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