apparmor profile ships 'local' override file, but doesn't #include it in the system profile

Bug #843552 reported by Chris Irwin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
Fix Released
Low
Jamie Strandboge

Bug Description

The package-installed apparmor profile included with telepathy-mission-control-5 (/etc/apparmor/usr.lib.telepathy) doesn't #include the local additions/override file (/etc/apparmor/local/usr.lib.telepathy), which does however exist. This means a user will have to modify a non-configuration file to make any policy changes. The documentation in /etc/apparmor/local/README indicates this should be avoided, leading me to believe the non-local files in /etc/apparmor are not protected as 'configuration' files by dpkg)

In a default install, the apport profiles for dhclient, firefox, cupsd, ntpd, and tcpdump all #include their respective local overrides, so this appears to be expected behaviour and definition of a profile.

Tags: apparmor
tags: added: apparmor
Changed in telepathy-mission-control-5 (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
importance: Undecided → Low
status: New → Triaged
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-mission-control-5 - 1:5.9.1-0ubuntu2

---------------
telepathy-mission-control-5 (1:5.9.1-0ubuntu2) oneiric; urgency=low

  * debian/apparmor-profile: include local/usr.lib.telepathy (LP: #843552)
 -- Jamie Strandboge <email address hidden> Wed, 07 Sep 2011 08:17:52 -0500

Changed in telepathy-mission-control-5 (Ubuntu):
status: In Progress → 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.