* debian/lib/apparmor/functions, debian/apparmor.init,
debian/apparmor.service, debian/apparmor.upstart,
debian/lib/apparmor/profile-load: Adjust the checks that previously kept
AppArmor policy from being loaded while booting a container. Now we
attempt to load policy if we're in a LXD or LXC managed container that is
using profile stacking inside of a policy namespace. (LP: #1628285)
* Fix regression tests so that the kernel SRU process is not interrupted by
failing tests
- debian/patches/r3505-tests-fix-stacking-mode-checks.patch: Fix the
stackonexec.sh and stackprofile.sh tests (LP: #1628295)
- debian/patches/r3509-tests-fix-exec_stack-errors.patch: Fix the
exec_stack.sh test (LP: #1628745)
This bug was fixed in the package apparmor - 2.10.95-4ubuntu5
---------------
apparmor (2.10.95-4ubuntu5) yakkety; urgency=medium
* debian/ lib/apparmor/ functions, debian/ apparmor. init, apparmor. service, debian/ apparmor. upstart, lib/apparmor/ profile- load: Adjust the checks that previously kept patches/ r3505-tests- fix-stacking- mode-checks. patch: Fix the ec.sh and stackprofile.sh tests (LP: #1628295) patches/ r3509-tests- fix-exec_ stack-errors. patch: Fix the
debian/
debian/
AppArmor policy from being loaded while booting a container. Now we
attempt to load policy if we're in a LXD or LXC managed container that is
using profile stacking inside of a policy namespace. (LP: #1628285)
* Fix regression tests so that the kernel SRU process is not interrupted by
failing tests
- debian/
stackonex
- debian/
exec_stack.sh test (LP: #1628745)
-- Tyler Hicks <email address hidden> Thu, 29 Sep 2016 00:38:47 -0500