This bug was fixed in the package apparmor - 2.3.1+1403-0ubuntu17
---
apparmor (2.3.1+1403-0ubuntu17) karmic; urgency=low
* abstractions/base: workaround for ecryptfs and apparmor by allowing
'owner' match for files in .Private. (LP: #359338)
-- Jamie StrandbogeMon, 31 Aug
For karmic we'll work around this with pure profiling. When the proper
userspace changes come from upstream we can remove the work around.
Those userspace changes will solve the stacked filesystems problem
generally, but require significant effort.
** Changed in: apparmor (Ubuntu Karmic)
Assi
Discussing this with John, the solution for Karmic does not require
kernel changes, so moving to AppArmor.
What does need to happen is that the AppArmor userspace needs to be
adjusted along with some small profiling work.
** Package changed: linux (Ubuntu Karmic) => apparmor (Ubuntu Karmic)
--
This behavior still exists in Jaunty and Karmic and it is going to be handled
in the user space at the policy level. The user space tools are being extended
to be able to handle, this in a couple of ways.
1. There will be a global policy file where rules like the work around
specified above c
** Changed in: linux (Ubuntu Karmic)
Status: Confirmed => In Progress
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Dustin,
it shouldn't matter where the encrypted data is placed, so this change
should not have any effect.
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Dustin,
it shouldn't matter where the encrypted data is placed, so this change
should not have any effect.
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
On Fri, Jul 17, 2009 at 10:17 AM, John
Johansen wrote:
> I have looked at this for Jaunty and have a patch that fixes this for all but
> 1 case in the kernel. That one case however requires a larger change and
> need further investigation. That one case still requires
> owner @{HOME}/.Private/*
I have looked at this for Jaunty and have a patch that fixes this for all but 1
case in the kernel. That one case however requires a larger change and need
further investigation. That one case still requires
owner @{HOME}/.Private/** rw, be added to profiles.
Testing in Karmic has shown that
** Changed in: linux (Ubuntu Karmic)
Assignee: (unassigned) => John Johansen (jjohansen)
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Also affects: ecryptfs-utils (Ubuntu Karmic)
Importance: High
Status: Invalid
** Also affects: linux (Ubuntu Karmic)
Importance: High
Status: Confirmed
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug n
** Summary changed:
- apparmor paths are broken when using encryptfs on jaunty
+ apparmor paths are broken when using ecryptfs on jaunty
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member o
12 matches
Mail list logo
