mirrors/apparmor
1
0
Fork 0
mirror of https://gitlab.com/apparmor/apparmor.git synced 2025-03-04 08:24:42 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update apparmorpolicyfeaturesABI

John Johansen 2020-07-05 22:37:21 +00:00
parent 37580ff827
commit b792ac9a5a
1 changed files with 1 additions and 23 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
apparmorpolicyfeaturesABI.md

@ -1,5 +1,6 @@
# AppArmor Feature ABI Table of Contents
- [Policy Feature ABI](AppArmorpolicyfeaturesabi) (This Document)
- [Feature ABI in AppArmor 2.x](AppArmor2FeatureABI)
- [Policy Feature ABI Interactions in Depth](AppArmorFeatureABIinteractions)
- [Policy Feature ABI low level examination](AppArmorFeatureABI)
- [AppArmor Versioning](Apparmorversioning)
@ -9,29 +10,6 @@
AppArmor uses features set ABIs to track what is supported???.
# AppArmor 2.x ABIs
The AppArmor series used a single feature ABI to determine what features where supported. When policy was compiled the ABI was checked for support of a given feature.
By default the compiler would use the feature ABI presented by the kernel, but the feature ABI could be changed by either specifying a specific ABI to the policy compiler (apparmor_parser) or Pinning the feature ABI.
## Specifying the feature ABI to the policy compiler
## Pinning
## Loading policy into the kernel
The kernel is often updated independent of the userspace. It is not uncommon to find new kernels being used on Linux distro userspaces that are several years old, because of this the apparmor kernel module supports multiple feature ABIs to remain backwards compatible with different userspaces.
enforce features policy wasn't designed for
fail to load policy
## Problems
### Policy not designed for the feature ABI
# Component ABI interaction