aboutsummaryrefslogtreecommitdiffstats
path: root/security/apparmor/match.c
diff options
context:
space:
mode:
authorJohn Johansen <john.johansen@canonical.com>2010-07-29 14:48:00 -0700
committerJames Morris <jmorris@namei.org>2010-08-02 15:38:37 +1000
commitc88d4c7b049e87998ac0a9f455aa545cc895ef92 (patch)
tree1859582b4afec1116b6831ea89ae27c35209991a /security/apparmor/match.c
parent736ec752d95e91e77cc0e8c97c057ab076ac2f51 (diff)
downloadkernel_samsung_smdk4412-c88d4c7b049e87998ac0a9f455aa545cc895ef92.zip
kernel_samsung_smdk4412-c88d4c7b049e87998ac0a9f455aa545cc895ef92.tar.gz
kernel_samsung_smdk4412-c88d4c7b049e87998ac0a9f455aa545cc895ef92.tar.bz2
AppArmor: core policy routines
The basic routines and defines for AppArmor policy. AppArmor policy is defined by a few basic components. profiles - the basic unit of confinement contain all the information to enforce policy on a task Profiles tend to be named after an executable that they will attach to but this is not required. namespaces - a container for a set of profiles that will be used during attachment and transitions between profiles. sids - which provide a unique id for each profile Signed-off-by: John Johansen <john.johansen@canonical.com> Signed-off-by: James Morris <jmorris@namei.org>
Diffstat (limited to 'security/apparmor/match.c')
0 files changed, 0 insertions, 0 deletions