bind9 should reload the named apparmor profile, not all of apparmor
Bug #412751 reported by
Jamie Strandboge
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Fix Released
|
Medium
|
Jamie Strandboge |
Bug Description
Binary package hint: bind9
Currently, bind9 will reload all of apparmor when it is upgraded. It should only reload its individual profile, otherwise after a bind9 upgrade, other apparmor protected applications will be unconfined until they are restarted.
Changed in bind9 (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
importance: | Undecided → Medium |
milestone: | none → karmic-alpha-5 |
status: | New → In Progress |
Changed in bind9 (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package bind9 - 1:9.6.1.dfsg.P1-3
---------------
bind9 (1:9.6.1.dfsg.P1-3) unstable; urgency=low
* Build-Depend on the fixed libgeoip-dev. Closes: #540973
bind9 (1:9.6.1.dfsg.P1-2) unstable; urgency=low
[Jamie Strandboge]
* reload individual named profile, not all of apparmor. LP: #412751
[Guillaume Delacour]
* bind9 did not purge cleanly. Closes: #497959
[LaMont Jones]
* postinst: do not append a blank line to /etc/default/bind9.
Closes: #541469
* init.d stop needs to not error out. LP: #398033
* meta: fix build-depends. Closes: #539230
-- LaMont Jones <email address hidden> Wed, 19 Aug 2009 22:47:32 +0100