Indeed https://bugs.launchpad.net/apparmor/+bug/1384746/comments/2
should be tracked else where. It really should split out into two
separate tracking issues.
1. either generating the feature file from the kernel on build. To track
this I have opened https://gitlab.com/apparmor/apparmor/-/issues/2
It seems to me this was fixed & released a while ago.
https://bugs.launchpad.net/apparmor/+bug/1384746/comments/2 could be
tracked on a new, follow-up bug, if still desired.
** Changed in: apparmor
Status: In Progress => Fix Released
--
You received this bug notification because you are
** Changed in: apparmor
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1384746
Title:
Support multiple versions of AppArmor policy cache files
Stat
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1384746
Title:
Support multiple versions of AppArmor policy cache file
Once the AppArmor parser supports multiple, versioned policy cache files
I will be adding the ability to generate the policy cache files at
kernel postinst. This will involve shipping a flattened AppArmor
features file in the Ubuntu kernel packages and then calling out to
apparmor_parser and specif
5 matches
Mail list logo
