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
What is the source of the referenced patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558079
Title:
cryptsetup tcryptOpen doesn't work anymore
To manage notifications about this bug go to:
htt
ok I see that appears to be the same patch as in comment #7. Michael,
has this 10_no_setkey_after_accept.patch patch been accepted upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558079
Titl
I'm on 14.04 (Trusty) and am still experiencing the same issue. I took
the patch from #7 and it fixes the issue for me. Unfortunately, without
you guys rolling updated libcryptsetup4 packages, I keep getting rolled
back to an unfixed version on every update. Subsequent kernel releases
(3.13.0-80 an
jduck on irc reports that he needs to use a locally-built cryptsetup
package with
https://launchpadlibrarian.net/249460666/10_no_setkey_after_accept.patch
included for it to function on 3.13.0-91-generic.
Foundations team, is there a chance for an SRU for this?
Thanks
--
You received this bug n
Thankfully linux-image-3.19.0-59 was part of the updates today, I am
able to access my volumes now. Thanks for the other advice, I'll keep
it handy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15580
New 3.19 and 3.13 upstream stable kernel should have patches that should
allow old cryptsetup to run again, just backport these patches on top of
accept fixes (instead of revert).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
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
I also received the error message, but with 3.19.0-58-generic. I'm unable to
revert back to 3.19.0-51 because some of drivers don't work with it anymore.
Required kernel crypto interface not available.
Ensure you have algif_skcipher kernel module loaded.
Let me know if there are are logs I can
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558079
Title:
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558079
Title:
cryptsetup tcryptOpen doesn't work anymore
To manage notifications
The attachment "do not alter the cryptd-socket after accepting it" seems
to be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Lau
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558079
Title:
cryptsetup tcryptOpen doesn't work anymore
To manage notifications about this bug go to:
https://bugs.launchpad.net
** 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 Ubuntu
Bugs, which is subscribed to Ubu
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
** Package changed: cryptsetup (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558079
Title:
cryptsetup tcryptOpen doesn't work anymore
To manage notifications about this
Booted up previous version, 3.19.0-51 and I confirm cryptsetup works fine with
tcrypt volume. So the bug has been introduced in 3.19.0-56 it seems.
Can always open volume with other tools, like truecrypt. So the problem is not
in the volume either.
Any info I could provide to help?
** Changed i
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.5 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
I tried the latest kernel (4.5.0-040500-generic) in a VM, and cryptsetup
does open fine a truecrypt disk.
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558079
T
20 matches
Mail list logo
