Public bug reported:
When apparmor is started, profiles are loaded but current target
processes are not protected. They have to be restarted in order to be
protected by their profile.
A consequence is that during the boot process, applications started
after apparmor are protected, but not applications started before. For
example, with the default profiles, ntpd is protected but not syslogd
and klogd. This is due to the order in which init scripts are started.
AppArmor may be started earlier in the boot process.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Profiles not applied to running processes when AppArmor is started
https://bugs.launchpad.net/bugs/116624
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
