Hi Ben, On Friday 05 February 2016 16:54:59 Ben Hutchings wrote: > On Fri, 2016-02-05 at 16:58 +0100, Carsten Wolff wrote: > > At least, it does not fix the error > > I'm seeing. The message stays the same, including the 32 byte it dumps. > > Then I'm out of ideas. I'll pass this to the upstream developers. here's an update on the issue: apparently, the latest wheezy-security kernel somehow broke padlock, too. I don't see any of the error messages I get with the jessie kernel, but after entering the key at the cryptsetup prompt, it responds with "No key available with this passphrase". I now have no kernel left to successfully boot with padlock/dm-crypt. One might think "hardware issue" now, but I can rule this out, it did work before and is still working in userspace (patched openssl package, apache/ openvpn using the openssl padlock engine). Regards Carsten
Attachment:
signature.asc
Description: This is a digitally signed message part.