Recent changes and apparmor policy loads
Zygmunt Krynicki
zygmunt.krynicki at canonical.com
Tue Apr 12 23:48:12 UTC 2016
On wto, 2016-04-12 at 16:42 -0500, Jamie Strandboge wrote:
> Hi,
>
> Recent snapd changes broke apparmor profile loading:
>
> * https://bugs.launchpad.net/snappy/+bug/1569573 - the apparmor
> systemd unit
> is looking in the wrong place for policy and doesn't load it on
> boot any
> more. This was caused by the recent path renames. Tyler Hicks is
> preparing
> an apparmor upload for this.
Thanks for finding and fixing this.
> * https://bugs.launchpad.net/snappy/+bug/1569581 - snapd no longer
> detects
> apparmor changes on upgrade. This was caused by the removal of a
> check. I'm
> not sure if interfaces is intended to handle this, but I don't
> think they
> will properly in their current form and I'm not sure how they
> could handle
> parser changes
Interfaces will handle that. As snapd starts up it will ensure that all
the apps the the expected profile and if needed, reload any changed
profiles.
Can you expand on the problem of parser changes?
Thanks
ZK
More information about the snappy-devel
mailing list