This bug appears in Jaunty if a new kernel is loaded - strace below. Is
it really "working as designed" if loading a new kernel causes dhcp to
fail?
508 execve("/sbin/dhclient-script", ["/sbin/dhclient-script"], [/* 4 vars */])
= 0
2508 brk(0)= 0x215c000
2508 fcntl(
** Branch linked: lp:ubuntu/dhcp3
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.
** Tags removed: regression-potential
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@li
Marking Jaunty dhcp3 task as Invalid since it is working as designed.
** Changed in: dhcp3 (Ubuntu Jaunty)
Status: New => Invalid
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you are a member of Ubuntu
Server Team
This is a bug in the handling of profile attachment for scripts. The
check to test if an attachment has already been applied needs to be
reworked for 2.6.28. This regression is mitigated, in that correct
attachment is retained if ix is used for the script interpreter which is
standard profiling p
This turns out to be a regression in Jaunty, that is now fixed and
behaving properly in Karmic
** Changed in: linux (Ubuntu Karmic)
Status: Confirmed => Invalid
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you are
** Also affects: dhcp3 (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you are a
This bug was fixed in the package dhcp3 - 3.1.2-1ubuntu4
---
dhcp3 (3.1.2-1ubuntu4) karmic; urgency=low
* Adjust dhclient AppArmor profile to call dhclient-script with Uxr instead
of Pxr with its own unrestricted profile. This simplifies the profile,
does not change the secu
** Also affects: dhcp3 (Ubuntu Karmic)
Importance: Medium
Assignee: Jamie Strandboge (jdstrand)
Status: Confirmed
** Also affects: linux (Ubuntu Karmic)
Importance: Medium
Assignee: John Johansen (jjohansen)
Status: Confirmed
--
dhclient-script fails with apparmor
h
Will solve this in dhcp3 profile in another way.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dhcp3 (Ubuntu)
Assignee: John Johansen (jjohansen) => Jamie Strandboge (jdstrand)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
Thanks for looking into this John, but I am rather baffled at this point
as to why the AppArmor behavior changed dramatically from Jaunty to
Karmic, when the script itself is the same. I also checked the full
delta between 3.1.1 (jaunty) and 3.1.2 (Karmic) and dhclient3 does not
change the way it c
I took a look at this and it is behaving correctly, though I haven't
established whether it is due to a deviation in AppArmor's behavior, the
scripts or both. The executable /sbin/dhclient3 does a Px transition
(as specified in its profile) to /sbin/dhclient-script.
/sbin/dhclient-script
I see this too. To reproduce, the network interface should not be
managed by Network Manager:
Then perform the following:
$ sudo /etc/init.d/NetworkManager stop
$ sudo ifconfig eth0 down
$ sudo dhclient eth0
I see the following in dmesg on i386:
[ 1482.018546] type=1503 audit(1247767237.673:10):
13 matches
Mail list logo
