diff options
author | Kees Cook <keescook@chromium.org> | 2017-05-13 04:51:45 -0700 |
---|---|---|
committer | Jonathan Corbet <corbet@lwn.net> | 2017-05-18 10:32:38 -0600 |
commit | 26fccd9ed2e283add2849858c28bd14f84d9c48e (patch) | |
tree | 4323d0eaf0687281391e76820ea59b28165858f7 /Documentation/security/apparmor.txt | |
parent | 229fd05c565eb931aa7c59c9d740e2047701a4ad (diff) | |
download | blackbird-op-linux-26fccd9ed2e283add2849858c28bd14f84d9c48e.tar.gz blackbird-op-linux-26fccd9ed2e283add2849858c28bd14f84d9c48e.zip |
doc: ReSTify apparmor.txt
Adjusts for ReST markup and moves under LSM admin guide.
Acked-by: John Johansen <john.johansen@canonical.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/security/apparmor.txt')
-rw-r--r-- | Documentation/security/apparmor.txt | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/Documentation/security/apparmor.txt b/Documentation/security/apparmor.txt deleted file mode 100644 index 93c1fd7d0635..000000000000 --- a/Documentation/security/apparmor.txt +++ /dev/null @@ -1,39 +0,0 @@ ---- What is AppArmor? --- - -AppArmor is MAC style security extension for the Linux kernel. It implements -a task centered policy, with task "profiles" being created and loaded -from user space. Tasks on the system that do not have a profile defined for -them run in an unconfined state which is equivalent to standard Linux DAC -permissions. - ---- How to enable/disable --- - -set CONFIG_SECURITY_APPARMOR=y - -If AppArmor should be selected as the default security module then - set CONFIG_DEFAULT_SECURITY="apparmor" - and CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 - -Build the kernel - -If AppArmor is not the default security module it can be enabled by passing -security=apparmor on the kernel's command line. - -If AppArmor is the default security module it can be disabled by passing -apparmor=0, security=XXXX (where XXX is valid security module), on the -kernel's command line - -For AppArmor to enforce any restrictions beyond standard Linux DAC permissions -policy must be loaded into the kernel from user space (see the Documentation -and tools links). - ---- Documentation --- - -Documentation can be found on the wiki. - ---- Links --- - -Mailing List - apparmor@lists.ubuntu.com -Wiki - http://apparmor.wiki.kernel.org/ -User space tools - https://launchpad.net/apparmor -Kernel module - git://git.kernel.org/pub/scm/linux/kernel/git/jj/apparmor-dev.git |