AFAIK there was no need for my patch to be included because the trusty
kernel maintainer reverted the upstream kernel.org changes to the kernel
which caused this bad behavior.
It seems like newer trusty kernels are affected again. (I'm not running
trusty with tcrypt-devices anymore, to test this b
No further logs are needed, the cause and several solution are known.
The error is caused by the fact that newer Kernels do not allow to
modify the cryptographic interface "kernel<->userspace" via
bind/setkey/... after accept(2) has been called. But the old cryptsetup
in trusty tahr is doing defin
** Patch added: "do not alter the cryptd-socket after accepting it"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558079/+attachment/4606459/+files/10_no_setkey_after_accept.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
With Ubuntu 14.04 and linux-image-3.13.0-83 it is caused by a kernel<->userland
breakage. See:
https://lkml.org/lkml/2015/12/29/383
It is caused by [crypto: af_alg - Disallow bind/setkey/... after accept(2)]
added to 3.13.0-80.124 with [ Upstream Kernel Changes ].
I've patched cryptsetup-1.6.1 t
Public bug reported:
I'm using cryptsetup to open TrueCrypt encrypted NTFS filesystems:
cryptsetup tcryptOpen /dev/sdf2 tcrypt
At least until linux-image-3.13.0-79-generic this work fine.
Booting linux-image-3.13.0-83-generic and running cryptsetup results in:
Required kernel crypto interface n
5 matches
Mail list logo
