From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smail.rz.tu-ilmenau.de (smail.rz.tu-ilmenau.de [141.24.4.149]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Fri, 20 Feb 2015 23:33:52 +0100 (CET) Received: from [192.168.66.2] (erft-5d809b91.pool.mediaWays.net [93.128.155.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smail.rz.tu-ilmenau.de (Postfix) with ESMTPSA id C2E2D5EEE0 for ; Fri, 20 Feb 2015 23:25:44 +0100 (CET) Message-ID: <54E7B46D.8060805@tu-ilmenau.de> Date: Fri, 20 Feb 2015 23:25:49 +0100 From: Lars Winterfeld MIME-Version: 1.0 References: <2E68FEAA-A69B-4E25-84F9-F30B2E7DFB69@gmail.com> In-Reply-To: <2E68FEAA-A69B-4E25-84F9-F30B2E7DFB69@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B4NtulNxtMetcqsfe55rRrvSMFRBNrN5x" Subject: Re: [dm-crypt] cryptsetup problem on Raspberry Pi 2 w 512bit key-size (works on Raspberry Pi 1, x86_64, 256bit) 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 4880 and 3156) --B4NtulNxtMetcqsfe55rRrvSMFRBNrN5x Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi. You could add another keyslot with a keyfile and open the device with that to be absolutely sure you did not just miss-type the password (because of a different keyboard layout on the Raspberry Pi 2 etc.) On 20.02.2015 22:37, Johannes Ernst wrote: > TL;DR:=20 > cryptsetup --hash sha512 --key-size 512 -v luksFormat ./test.img > cannot be opened again on the new Raspberry Pi 2. Shorter key-size, and= other platforms work. >=20 > This is a bit a puzzler to me =E2=80=A6 >=20 > This is what I do: > # Create 8M image > dd if=3D/dev/zero of=3D./test.img count=3D8 bs=3D1M > # Set up encryption -- enter a suitable password when asked > cryptsetup --hash sha512 --key-size 512 -v luksFormat ./test.img > # Now attempt to open it, entering the same password > cryptsetup open test.img test >=20 > and indeed it works for me on x86_64, the Raspberry PI 1, and the Beagl= eBone Black. However, it fails on the Raspberry Pi 2 with: > "No key available with this passphrase." >=20 > If I create the encrypted image on the Raspberry Pi 2, I can open it on= other platforms. However, I cannot open any image with these parameters = on the Raspberry Pi 2, regardless where it was created. >=20 > If I set the key-size to 256 bit, it works on all platforms. >=20 > The Raspberry Pi 2 is an ARM v7 processor, unlike the Raspberry Pi 1. B= ut then, the BeagleBone Black is Arm V7, too. >=20 > Puzzled ... >=20 >=20 >=20 >=20 > Johannes. >=20 > _______________________________________________ > dm-crypt mailing list > dm-crypt@saout.de > http://www.saout.de/mailman/listinfo/dm-crypt >=20 --B4NtulNxtMetcqsfe55rRrvSMFRBNrN5x Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJU57RtAAoJEA4jvzLPLJH4OZ0QALPGLvr7kLvetp17o6eNiD9A 3KS9eep9Mnm+7m+GHPFPcJlchsD/RNrvp2A6tpbOoXxDRYFr4LRY0zB+/WAPSa9j nkCM1EBmPm4Fr+v60choLXaX7n5aGVVkBN/Tf1LLUiI8CYKPwCWrNbMF++++19+N 16/mThFAKRG37bVdFbZroSz9Sm67bwqlfCsA0at4vhueLhBrq9OSco1d5BoJ5hzu SWiGt9XxMqj5CQwkVLrxHaX77HQW9Flj1PfHLvDaBo1/6/wmrtmGV7fyECW66cR6 MiaRc+6bOT+BONaAC4nm8j5KnkRZXcPvRAiNijISmOvhSlcGdewVLY+L81HFrowo MAfa0FXfYFv2jFD5aqyg6aPlR7mrbrGvLpPUimo98BUn4iQ/KzqhQPAQRM3QVyJn /0G3OyavNwDJhrcLU/5FmeJKeBkcoLaa7QCJFjMQd9bK6LZr6Fh0qGpItcsjAJIR hWBjJR9i60+Uj5ud46B4sCeZRe6n/g46qwKNqIXO+jSJJ1RUq77rpr2X8DVuBcUa zWqR/Nnfqv3/zog6xBhComciX+p4tmFdQY7HCi8/zDm9ZPeuDa+mrZAlR4zy7VqH rxKlCUz/j2ew6HoTktoVdO8vICNnnAxh+JK4ZSbC80GQ/71/MKEEK26nT3rir0Mx bBlECW8WKXnrmcG4JdJc =7ww8 -----END PGP SIGNATURE----- --B4NtulNxtMetcqsfe55rRrvSMFRBNrN5x--