
TIP: Background Information for Novell AppArmor
To get a more in-depth overview of AppArmor and the overall concept behind
it, refer to
Appendix A, Background Information on AppArmor Profiling
(page 119).
1.1 Introducing the AppArmor
Framework
The following section provides you with a very basic understanding of what is happening
“behind the scenes” (and under the hood of the YaST interface) when you run App-
Armor.
An AppArmor profile is a plain text file containing path entries and access permissions,
see
Section 2.1, “Breaking a Novell AppArmor Profile into Its Parts”
(page 19) for a
detailed reference profile. The directives contained in this text file are then enforced
by the AppArmor routines to quarantine the process/program.
The following tools interact in the building and enforcement of AppArmor profiles and
policies:
aa-unconfined
aa-unconfined detects any application running on your system that listens for net-
work connections and is not protected by an AppArmor profile. Refer to
Section
“aa-unconfined—Identifying Unprotected Processes”
(page 67) for detailed infor-
mation on this tool.
aa-autodep
aa-autodep creates a basic skeleton of a profile that needs to be fleshed out before
it is put to productive use. The resulting profile is loaded and put into complain
mode, reporting any behavior of the application that is not (yet) covered by App-
Armor rules. Refer to
Section “aa-autodep—Creating Approximate Profiles”
(page 52) for detailed information on this tool.
aa-genprof
aa-genprof generates a basic profile and asks you to refine this profile by executing
the application and thus generating log events that need to be taken care of by
10
Novell AppArmor Administration Guide