apparmor(7) is not clear about the effect of reloading a profile

Bug #1608075 reported by intrigeri
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppArmor
Fix Released
Undecided
Unassigned

Bug Description

apparmor(7) reads:

       Profiles are applied to a process at exec(3) time (as seen through the
       execve(2) system call); an already running process cannot be confined.
       However, once a profile is loaded for a program, that program will be
       confined on the next exec(3).

The way I understood it, this implies that a modified+reloaded profile will only be applied to the confined program next time it is executed.

And then I was kindly explained that I got it wrong, and that the manpage was not clear about it:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826218#100

Revision history for this message
intrigeri (intrigeri) wrote :
intrigeri (intrigeri)
Changed in apparmor:
status: New → 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.