[Bug 446449] Re: [Karmic] After restarting AppArmor, aa-logprof doesn't seem to load the existing profiles.

[Marc Deslauriers]

SRU Nomination:

Impact: AppArmor user-space tool to generate new profiles does not work
as expected. The "aa-logprof" tool doesn't read in existing profiles,
will ask confirmation for every log entry it finds, and will generate a
broken profile.

Bug: SubDomain.pm would skip reading in profiles that were located in
the cache directory, instead of skipping _files_ that were in the cache
directory. Fixing this bug uncovered two parsing bugs with new profiles
that were introduced in the Karmic timeline: PUxr modes and include
directories.

Patch: http://bazaar.launchpad.net/~ubuntu-core-dev/apparmor/ubuntu-
karmic/revision/1057

Reproduce instructions:

1- Generate a new profile with aa-genprof. Answer all questions, and save profile
2- Restart AppArmor
3- Run aa-logprof.
4- Expected behaviour: aa-logprof should reparse log entries and everything should already be in the saved profile.
5- Buggy behaviour: aa-logprof will ask the user to confirm modifications to the profile.

Regression potential: This patch only modifies the tools to generate new
profiles. Regular users will not be affected by this change. For users
who are trying to generate an AppArmor profile, the tools are currently
broken as it is.

-- 
[Karmic] After restarting AppArmor, aa-logprof doesn't seem to load the existing profiles.
https://bugs.launchpad.net/bugs/446449
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs