Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as "Won't Fix".
** Changed in: cupsys (Ubuntu Karmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as "Won't Fix".
** Changed in: dhcp (Ubuntu Karmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: apparmor (Ubuntu Karmic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/131976
Title:
apparmor doesn't work on stacked file system (livecd) --
** Tags added: karmic regression-release
** Tags removed: regression-potential
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/131976
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
If you look at "sudo aa-status", I would expect that DHCP and CUPS are not
actually being confined by AppArmor, so there aren't errors. If you
restart the network or CUPS after starting AppArmor in the LiveCD, I would
expect those services to start failing. If that's _not_ the case, then
this sho
IF the problem is the stacked file system, then why am I able to, after
booting, do:
sudo /etc/init.d/apparmor start
on my persistent 9.10 Live CD and have no errors?
Is it possible that this 'bug' with the stacked file system is just a
problem caused by the Ubuntu initrd.lz trying to load appa
On Tue, Jun 22, 2010 at 02:45:13AM -, Sid MacT wrote:
> Is it possible that simply changing the apparmor profile load process to
> follow the creation of the union file system, would allow apparmor to
> execute properly? It seems like an odd coincidence that lots of software
> EXCEPT apparmor a
Is it possible this problem is caused by a sequencing problem with the
Live CD scripts? I run the Karmic LiveCD in persistent mode on a hard
disk drive. Once I am logged in to Ubuntu, I can run 'sudo
/etc/init.d/apparmor start' and see no errors in the terminal nor the
log files. The kernel log sho
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/131976
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
unassigned MOTU, invalidated wrong dhcp & cupsys tasks
** Changed in: cupsys (Ubuntu)
Assignee: MOTU (motu) => (unassigned)
** Changed in: dhcp (Ubuntu)
Assignee: MOTU (motu) => (unassigned)
** Changed in: cupsys (Ubuntu)
Status: New => Invalid
** Changed in: dhcp (Ubuntu)
Right I messed up the alias order but there is still a bug in alias processing,
that needs to be fixed before this will work. Basically setting
alias /etc -> /rofs/etc,
will result in rejections for accesses to /etc/ instead of /rofs/etc/
--
apparmor doesn't work on stacked file system (live
On Wed, Feb 10, 2010 at 03:46:42PM -, Nikolaus Rath wrote:
> It still does not work:
>
> [0] matterhorn[ltsp]:~# cat /etc/apparmor.d/tunables/alias
> # https://bugs.launchpad.net/bugs/131976
> alias file
> alias /rofs -> /,
> alias /cow -> /,
Err, the alias mappings should be the other round
Nikolaus,
thanks, it looks like you have hit a bug in the alias command, I'll look
into this and see if I can't get something for you to test in the next
couple of days.
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/13
** Attachment added: "/etc/apparmor.d/sbin.dhclient3"
http://launchpadlibrarian.net/39015066/sbin.dhclient3
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/131976
You received this bug notification because you are a m
It still does not work:
[0] matterhorn[ltsp]:~# cat /etc/apparmor.d/tunables/alias
# https://bugs.launchpad.net/bugs/131976
alias file
alias /rofs -> /,
alias /cow -> /,
[0] matterhorn[ltsp]:~# /etc/init.d/apparmor restart
* Reloading AppArmor profiles
Nikolaus,
did you restart apparmor after making the change? The profiles will have to be
reloaded.
> sudo /etc/init.d/apparmor restart
if that doesn't work can you attach your profiles
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.lau
Doesn't seem to help:
[0] matterhorn[ltsp]:~# /sbin/dhclient3
/sbin/dhclient3: error while loading shared libraries: libc.so.6: cannot open
shared object file: No such file or directory
[127] matterhorn[ltsp]:~# cat /etc/apparmor.d/tunables/alias
# https://bugs.launchpad.net/bugs/131976
alias fi
** Also affects: cupsys (Ubuntu)
Importance: Undecided
Status: New
** Also affects: dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cupsys (Ubuntu)
Assignee: (unassigned) => MOTU (motu)
** Changed in: dhcp (Ubuntu)
Assignee: (unassigned) => MOTU (motu
Nikolaus upstream does watch here and track bugs filed in launchpad.
This particular issue arise due to the LSM not providing AppArmor
sufficient information about access on stacked file systems. You can
mostly work around the issue using the alias command
can you try adding the following command
Note that this is not on the LiveCD, but on a LTSP client. Root is a
unionfs of /rofs (NFS) and /cow (tmpfs).
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/131976
You received this bug notification because you are a mem
I am still experiencing this problem:
# ifup eth1
dhclient3: error while loading shared libraries: libc.so.6: cannot open shared
object file: No such file or directory
Failed to bring up eth1.
# dmesg | tail
[ 226.453040] type=1503 audit(1265397277.944:30): operation="open" pid=2983
parent=298
Turning apparmor off on the LiveCD is ignoring the underlying problem
that apparmor doesn't work on stacked file systems. I'm currently
developing a system that uses aufs as the root file system, and there's
no way to use apparmor with it. I assume this is a bug that would need
to be fixed upstream
This bug was fixed in the package apparmor - 2.3.1+1403-0ubuntu22
---
apparmor (2.3.1+1403-0ubuntu22) karmic; urgency=low
* Do not run AppArmor on the LiveCD, again (LP: #131976).
* More aggressively stay quiet when booting in quiet mode (LP: #435285).
-- Kees CookWed, 23 Se
Yes, this is related to moving AppArmor init into the initramfs. I'll
have it uploaded shortly.
** Changed in: apparmor (Ubuntu Karmic)
Status: Triaged => In Progress
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/b
** Branch linked: lp:~ubuntu-core-dev/apparmor/ubuntu
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/131976
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Tentatively assigning to Kees, please assing to someone appropriate
(Johan?)
** Changed in: apparmor (Ubuntu Karmic)
Assignee: (unassigned) => Kees Cook (kees)
** Changed in: apparmor (Ubuntu Karmic)
Milestone: None => ubuntu-9.10-beta
** Tags added: regression-potential
** Tags removed
26 matches
Mail list logo
