mirror of
https://gitlab.com/apparmor/apparmor
synced 2025-08-22 01:57:43 +00:00
Update apparmorversioning
parent
afd42f892a
commit
ab059922f4
@ -1,15 +1,22 @@
|
||||
# Introduction
|
||||
|
||||
When working with AppArmor their are many independent or semi-independent components and it can be important to understand how they interact. Generally version numbering is used to provide a coarse indication of a components progression but does not usually provide???
|
||||
|
||||
Lots of different versioning to deal with
|
||||
|
||||
parser, kernel, policy, library, tools,
|
||||
|
||||
dependencies
|
||||
- requires
|
||||
- suggests
|
||||
- breaks
|
||||
|
||||
|
||||
profiles can be split into 2 main sets. Base application permissions, configuration permissions, dynamic runtime permission (changes based on inputs).
|
||||
|
||||
# Applications versions
|
||||
|
||||
AppArmor policy is not tied to an application version, however changes to an application may necessitate changes to the apparmor policy.
|
||||
|
||||
- libs may require changes as well
|
||||
AppArmor policy is not tied to an application version, however changes to an application or its libraries may necessitate changes to the apparmor policy.
|
||||
|
||||
package with application
|
||||
system package separate from application
|
||||
|
Loading…
x
Reference in New Issue
Block a user