** Information type changed from Private Security to Public Security
** Package changed: ubuntu => apparmor (Ubuntu)
** Changed in: apparmor (Ubuntu)
Status: Expired => Won't Fix
** Changed in: apparmor (Ubuntu)
Status: Won't Fix => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1594695
Title:
apparmor service not started on fresh install
Status in apparmor package in Ubuntu:
New
Bug description:
On fresh install of LXC, apparmor service (a dependency) is not
started. In that case, it causes LXC guest startup to fail. apparmor
postinstall seems only to configure the service but does not start it:
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ]; then
if [ -x "/etc/init.d/apparmor" ]; then
update-rc.d apparmor start 37 S . >/dev/null || true
fi
fi
To me it is not clear, if this is just an apparmor/lxc combination
issue or may affect apparmor installs in general: in later case,
machines might be unprotected till the first reboot (which might be
quite some time on servers when there are no upstream security fixes
requiring reboot).
# lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
# apt-cache policy apparmor
apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
*** 2.10.95-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1594695/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
