This bug was fixed in the package linux - 2.6.28-7.18
---
linux (2.6.28-7.18) jaunty; urgency=low
[ Alok Kataria ]
* SAUCE: (drop after 2.6.29) x86: add a synthetic TSC_RELIABLE feature
bit
- LP: #319945
* SAUCE: (drop after 2.6.29) x86: add X86_FEATURE_HYPERVISOR featu
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
jaunty.git;a=commit;h=e8782a447782a69b423bb91741d2669018eef899
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
Target: jaunty-alpha-4 => jaunty-alpha-5
--
ecryptfs does not handle symlinks within bzr
https://bugs.launchpa
I'm marking the bzr task 'invalid', and assigning the kernel task to
Tim.
I'm also going to mark the ecryptfs-utils (userspace) task invalid as
well, since it's a bug in the kernel space.
:-Dustin
** Changed in: bzr (Ubuntu)
Status: New => Invalid
** Changed in: ecryptfs-utils (Ubuntu)
Cool, thanks for the explanation, Martin.
Actually, bzr has revealed a bug deeply buried in our code ;-) Thanks
for that!
:-Dustin
** Changed in: linux (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Tim Gardner (timg-tpi)
Status: New => Triaged
Target: No
I have looked at our source and I think bzr is just doing the equivalent
of
python -c 'import os;print repr(os.readlink("foo"))'
so you should be able to test if that causes a problem. My guess is
that Python, which can handle strings with embedded nuls, is (perhaps
reasonably) giving back "ba
Awesome, thanks for tracking that down, Tyler.
I have subscribed Tim Gardner to the bug. Hopefully he can apply that
to our kernel soon.
Thanks,
:-Dustin
--
ecryptfs does not handle symlinks within bzr
https://bugs.launchpad.net/bugs/322532
You received this bug notification because you are a
** Attachment added: "This patch fixes the problem. It applies against
2.6.29-rc3, but may or may not apply against the Ubuntu kernel. I will test a
little more before sending it upstream."
http://launchpadlibrarian.net/21787775/0001-eCryptfs-Regression-in-unencrypted-filename-symlin.patch
Thanks for the bug report Jamie, this one would have been easily to slip
by.
It looks like an off-by-one error in the eCryptfs kernel code. We're
tacking on an extra byte to the symlink target. Dustin pointed this out
to me and I was able to verify it with `strace readlink -n bar`. Here's
the i
Jamie-
A few notes...
* I'm going to add bzr to the affected packages, in case those guys have an
idea of what might be going on, and what this error actually means. Its
possible that bzr is doing something "smart" by looking at underlying data,
perhaps?
This looks to be a regression in th
** Also affects: bzr (Ubuntu)
Importance: Undecided
Status: New
--
ecryptfs does not handle symlinks within bzr
https://bugs.launchpad.net/bugs/322532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: "bzr_links.tar.gz"
http://launchpadlibrarian.net/21748467/bzr_links.tar.gz
--
ecryptfs does not handle symlinks within bzr
https://bugs.launchpad.net/bugs/322532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
11 matches
Mail list logo
