Return-Path: Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mail.saout.de (Postfix) with SMTP for ; Fri, 28 May 2010 11:06:46 +0200 (CEST) Message-ID: <4BFF87A4.1060000@gmx.net> Date: Fri, 28 May 2010 11:06:44 +0200 From: "Nico R." MIME-Version: 1.0 References: <4BFDA544.1060707@gmx.net> <4BFE3967.6030703@redhat.com> <4BFF801D.3060100@gmx.net> <4BFF824F.8070607@redhat.com> In-Reply-To: <4BFF824F.8070607@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC366C92FA8EE40D1CDB5FFBA" Subject: Re: [dm-crypt] Problem with piped passphrases containing newline character List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC366C92FA8EE40D1CDB5FFBA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2010-05-28T08:43:59Z, Milan Broz wrote: > 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. >>> [=E2=80=A6] >=20 > Well, ok. It should be fixed in current devel code anyway. >=20 > http://code.google.com/p/cryptsetup/source/detail?r=3D237 Thanks. The added test code in /trunk/tests/compat-test looks good. If I read it correctly, luksFormat can now also use the --key-file option. This should be added to the man page before a release, I think. --=20 Nico --------------enigC366C92FA8EE40D1CDB5FFBA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEARECAAYFAkv/h6QACgkQxI5uhYOGv4XT5wCgm+NGSefaWcB3ngaUHw7Y+HDp tpsAnj9XaEMHb6ZOaTTiP6So3fnGIph8 =XOaV -----END PGP SIGNATURE----- --------------enigC366C92FA8EE40D1CDB5FFBA--