2.2.1 Abstractions
Abstractions are
#include
s that are grouped by common application tasks. These
tasks include access to authentication mechanisms, access to name service routines,
common graphics requirements, and system accounting. Files listed in these abstractions
are specific to the named task. Programs that require one of these files usually require
some of the other files listed in the abstraction file (depending on the local configuration
as well as the specific requirements of the program). Find abstractions in
/etc/
apparmor.d/abstractions
.
2.2.2 Program Chunks
The program-chunks directory (
/etc/apparmor.d/program-chunks
) contains
some chunks of profiles that are specific to program suites and not generally useful
outside of the suite, thus are never suggested for use in profiles by the profile wizards
(aa-logprof and aa-genprof). Currently program chunks are only available for the
postfix program suite.
2.3 Capability Entries (POSIX.1e)
Capabilities statements are simply the word
capability
followed by the name of
the POSIX.1e capability as defined in the
capabilities(7)
man page.
2.4 Using the Local AppArmor Profile
Repository
AppArmor ships a set of profiles enabled by default and created by the AppArmor de-
velopers and kept under the
/etc/apparmor.d
. In addition to these profiles, open-
SUSE ships profiles for individual applications together with the respective application.
These profiles are not enabled by default and reside under another directory than the
standard AppArmor profiles,
/etc/apparmor/profiles/extras
.
The AppArmor tools, both YaST and aa-genprof and aa-logprof, support the use of a
local repository. Whenever you start to create a new profile from scratch and there al-
22
Novell AppArmor Administration Guide