aa-audit: no warning for disabled profiles

Bug #1429448 reported by Christian Boltz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppArmor
Fix Released
Undecided
Christian Boltz

Bug Description

If a disable symlink for a profile exists, aa-audit will still print "Setting $profile to audit mode.", but the parser won't load it into the kernel because of the disable symlink. While this is technically correct, the result might still be surprising for some users.

Is there a way to get a warning like "The profile is disabled, not loading it" from the parser?

Possible solutions:
- a parser option to print a warning for disabled profiles (off by default)
- additional code in aa-audit that checks if a disable symlink exists, and prints the warning itsself

Christian Boltz (cboltz)
Changed in apparmor:
assignee: nobody → Christian Boltz (cboltz)
status: New → In Progress
Christian Boltz (cboltz)
Changed in apparmor:
status: In Progress → Fix Committed
milestone: none → 2.10
Revision history for this message
Steve Beattie (sbeattie) wrote :

AppArmor 2.10 has been released: https://launchpad.net/apparmor/2.10/2.10

Changed in apparmor:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.