[Karmic] After restarting AppArmor, aa-logprof doesn't seem to load the existing profiles.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apparmor (Ubuntu) |
Fix Released
|
Medium
|
Marc Deslauriers | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apparmor
When I attempt to create a new profile with the "aa-genprof" command, I find that none of the changes I make through the interactive apparmor log parser stick (I am using the auditd, by the way). If I try to generate a profile for my IRC client, for example, I find that whenever I perform "aa-logprof" that I get asked the same questions over and over again. They do not stick, even after restarting apparmor or even after rebooting. And I get the following error when I try to restart apparmor whenever one of my generated profiles exists in /etc/apparmor.d/:
sudo /etc/init.
* Reloading AppArmor profiles
Found reference to variable HOME, but is never declared
Found reference to variable HOME, but is never declared
The above error implies that the #include <tunables/global> line was not included in the profile. If I add that line, it fixes the problem temporarily, but after I run aa-logprof again, I encounter the same audit logs again and again. Further, when I restart apparmor, I find that the #include <tunables/global> line has disappeared from my profile.
Also, when I try to put all profiles into enforce mode, I get a bit more detailed of an error:
sudo aa-enforce /etc/apparmor.d/*
Setting /etc/apparmor.
/sbin/apparmor_
Found reference to variable HOME, but is never declared
So, basically, AppArmor profile generation in Karmic is broken.
Here is my uname -a:
Linux 2.6.31-12-generic #41-Ubuntu SMP Wed Oct 7 19:37:12 UTC 2009 x86_64 GNU/Linux
tags: | added: apparmor |
I can reproduce the problem on Karmic. Once you've generated a profile with aa-genprof, aa-logprof will parse the log files properly.
If you restart apparmor "/etc/init. d/apparmor restart", aa-logprof will ask for confirmation on every log entry it finds and will break the profile.
I'll investigate this.