isc-dhcp-server apparmor include
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
Fix Released
|
Undecided
|
Unassigned | ||
apparmor (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I tried to put isc-dhcp-server in to complain mode due to issues with /run and /var/run PID flags.
It gave me an error
root@here:
Setting /etc/apparmor.
Traceback (most recent call last):
File "/usr/sbin/
tool.
File "/usr/lib/
raise apparmor.
apparmor.
due to #include <dhcpd.d> in usr.sbin.dhcpd
Two things confuse me. The use of '#' and '# ' to mean include and for commenting respectively. Is this not going to make bug fixing more difficult ?
and two should dhcpd.d include a full path ?
Why is app armour complain complaining with a standard file ?
Cheers
Simon
affects: | isc-dhcp (Ubuntu) → apparmor (Ubuntu) |
Hi Simon. Sorry for the difficulty you encountered. The specific traceback issue you encountered with aa-complain has been addressed in trusty in apparmor-utils and python3-apparmor 2.8.95~ 2430-0ubuntu5. 2, so I'm closing this bug (it was also fixed upstream in the 2.9.2 and 2.10 releases).
Yes, the use of c-style #include and shell style # prefix for comments is a bit confusing. AppArmor 2.10 which will be in ubuntu 15.10 includes support for just using the keyword 'include' instead of "#include' (though the latter will still work).
The "dhcpd.d" include is assuming the base path to look for included files and directories is /etc/apparmor.d/. In this case, the include references the directory /etc/apparmor. d/dhcpd. d/ which tells apparmor to include any files in that directory into the profile. However, the aa-complain tool before 2.8.95~ 2430-0ubuntu5. 2 did not support including directories, which is why it crashed.
Thanks!