Load the transmission-daemon apparmor profile in the upstart init configuration file.

Bug #1228487 reported by David
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am using the apparmor transmission-daemon profile attached to this bug report and on boot it is not 'applied' because the transmission-daemon can start up before its apparmor profile is loaded. This issue can normally be fixed by adding a /lib/init/apparmor-profile-load $profile_name to the upstart configuration pre-start script.

Revision history for this message
David (d--) wrote :

Actually I am not sure that this bug is best fixed this way. Unfortunately the pre-start script is not able to load the apparmor profile because the upstart setuid and setgid directives have already been applied. So instead this bug can be fixed by including a symbolic link to the transmission-daemon apparmor profile in /etc/apparmor/init/network-interface-security/ .

Revision history for this message
David (d--) wrote :
description: updated
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.