Novell APPARMOR - AND Manuel utilisateur
This document helps you understand the main concepts behind Novell® AppArmor—the content of AppArmor
proles. Learn how to create or modify AppArmor proles. You can create and manage AppArmor proles in
three different ways. The most convenient interface to AppArmor is provided by means of the AppArmor YaST
modules which can be used either in graphical or ncurses mode. The same functionality is provided by the
AppArmor command line tools or if you just edit the proles in a text editor.
AppArmor Modes
complain/learning
In complain or learning mode, violations of AppArmor
prole rules, such as the proled program accessing les
not permitted by the prole, are detected. The violations
are permitted, but also logged. This mode is convenient
for developing proles and is used by the AppArmor
tools for generating proles.
enforce
Loading a prole in enforcement mode enforces the
policy dened in the prole as well as reports policy vi-
olation attempts to syslogd.
Starting and Stopping AppArmor
Use the rcapparmor command with one of the following
parameters:
start
Load the kernel module, mount securityfs, parse and
load proles. Proles and connement are applied to
any application started after this command was executed.
Processes already running at the time AppArmor is
started continue to run unconned.
stop
Unmount securityfs, and invalidate proles.
reload
Reload proles.
status
If AppArmor is enabled, output how many proles are
loaded in complain or enforce mode.
Use the rcaaeventd command to control event logging
with aa-eventd. Use the start and stop options to toggle
the status of the aa-eventd and check its status using the
status.
AppArmor Command Line Tools
autodep
Guess basic AppArmor prole requirements. autodep
creates a stub prole for the program or application
examined. The resulting prole is called “approximate”
because it does not necessarily contain all of the prole
entries that the program needs to be conned properly.
complain
Set an AppArmor prole to complain mode.
Manually activating complain mode (using the command
line) adds a ag to the top of the prole so that
/bin/foo becomes /bin/foo flags=(complain).
enforce
Set an AppArmor prole to enforce mode from complain
mode.
Novell AppArmor (for SLE 10 SP2)
Quick Start
NOVELL® QUICK START CARD
1
Manually activiating enforce mode (using the command
line) removes mode ags from the top of the prole
/bin/foo flags=(complain) becomes /bin/foo.
genprof
Generate or update a prole. When running, you must
specify a program to prole. If the specied program is
not an absolute path, genprof searches the $PATH vari-
able. If a prole does not exist, genprof creates one using
autodep.
logprof
Manage AppArmor proles. logprof is an interactive tool
used to review the learning or complain mode output
found in the AppArmor syslog entries and to generate
new entries in AppArmor proles.
unconned
Output a list of processes with open tcp or udp ports
that do not have AppArmor proles loaded.
Methods of Proling
Stand-Alone Proling
Using genprof. Suitable for proling small applications.
Systemic Proling
Suitable for proling large numbers of programs all at
once and for proling applications that may run “forev-
er.”
To apply systemic proling, proceed as follows:
1. Create proles for the individual programs that make
up your application (autodep).
2. Put relevant proles into learning or complain mode.
3. Exercise your application.
4. Analyze the log (logprof).
5. Repeat Steps 3-4.
6. Edit the proles.
7. Return to enforce mode.
8. Reload all proles (rcapparmor restart).
Learning Mode
When using genprof, logprof, or YaST in learning mode,
you get several options for how to proceed:
Allow
Grant access.
Deny
Prevent access.
Glob
Modify the directory path to include all les in the sug-
gested directory.
Glob w/Ext
Modify the original directory path while retaining the
lename extension. This allows the program to access
all les in the suggested directories that end with the
specied extension.
Edit
Enable editing of the highlighted line. The new (edited)
line appears at the bottom of the list. This option is called
New in the logprof and genprof command line tools.
Abort
Abort logprof or YaST, losing all rule changes entered
so far and leaving all proles unmodied.
Finish
Close logprof or YaST, saving all rule changes entered
so far and modifying all proles.
Example Prole
# a variable definition
@{HOME} = /home/*/ /root/
# a comment about foo.
/usr/bin/foo {
/bin/mount ux,
/dev/{,u}random r,
/etc/ld.so.cache r,
/etc/foo.conf r,
/etc/foo/* r,
/lib/ld-*.so* mr,
/lib/lib*.so* mr,
/proc/[0-9]** r,
/usr/lib/** mr,
/tmp/ r,
/tmp/foo.pid wr,
/tmp/foo.* lrw,
/@{HOME}/.foo_file rw,
/@{HOME}/.foo_lock w,
# a comment about foo's subprofile, bar.
^bar {
/lib/ld-*.so* mr,
/usr/bin/bar px,
/var/spool/* rwl,
}
}
Structure of a Prole
Proles are simple text les in the /etc/apparmor.d di-
rectory. They consist of several parts: #include, capability
entries, rules, and “hats.”
#include
This is the section of an AppArmor prole that refers to an
include le, which mediates access permissions for pro-
grams. By using an include, you can give the program access
to directory paths or les that are also required by other
programs. Using includes can reduce the size of a prole.
It is good practice to select includes when suggested.
2
To assist you in proling your applications, AppArmor pro-
vides three classes of #includes: abstractions, program
chunks, and variables.
Abstractions are #includes that are grouped by common
application tasks. These tasks include access to authentica-
tion mechanisms, access to name service routines, common
graphics requirements, and system accounting, for example,
base, consoles, kerberosclient, perl, user-mail, user-tmp,
authentication, bash, nameservice.
Program chunks are access controls for specic programs
that a system administrator might want to control based
on local site policy. Each chunk is used by a single program.
Using variables, you can design your proles to be portable
to different environments. Changes in the variable's content
are just made in the variable denition while the prole
containing the variable can remain untouched.
Capability Entries (POSIX.1e)
Capabilities statements are simply the word “capability”
followed by the name of the POSIX.1e capability as dened
in the capabilities(7) man page.
Rules: General Options for Files and
Directories
FileOption
rread
wwrite
llink
Rules: Dening Execute Permissions
For executables that may be called from the conned pro-
grams, the prole creating tools ask you for an appropriate
mode, which is also reected directly in the prole itself:
DescriptionFileOption
Stay in the same (parent's) prole.ixInherit
Requires that a separate prole ex-
ists for the executed program. No
environment scrubbing.
pxProle
Requires that a separate prole ex-
ists for the executed program. Uses
environment scrubbing.
PxProle
Executes the program without a
prole. Avoid running programs in
uxUncon-
strained
unconstrained or unconned mode
for security reasons. No environ-
ment scrubbing.
Executes the program without a
prole. Avoid running programs in
UxUncon-
strained
unconstrained or unconned mode
DescriptionFileOption
for security reasons. This mode
makes use of environment scrub-
bing.
allow PROT_EXEC with mmap(2)
calls
mAllow Exe-
cutable Map-
ping
WARNING: Running in ux Mode
Avoid running programs in ux mode as much as
possible. A program running in ux mode is not only
totally unprotected by AppArmor, but child process-
es inherit certain environment variables from the
parent that might inuence the child's execution
behavior and create possible security risks.
For more information about the different le execute
modes, refer to the apparmor.d(5) man page. For more
information about setgid and setuid environment scrubbing,
refer to the ld.so(8) man page.
Rules: Paths and Globbing
DescriptionGlob
Substitutes for any number of characters,
except /.
*
Substitutes for any number of characters,
including /.
**
Substitutes for any single character, ex-
cept /.
?
Substitutes for the single character a,b,
or c.
[ abc ]
Substitutes for the single character a,b,
or c.
[ a-c ]
Expand to one rule to match ab and an-
other to match cd.
{ ab,cd }
Hats
An AppArmor prole represents a security policy for an
individual program instance or process. It applies to an ex-
ecutable program, but if a portion of the program needs
different access permissions than other portions, the pro-
gram can “change hats” to use a different security context,
distinctive from the access of the main program. This is
known as a hat or subprole.
A prole can have an arbitrary number of subproles, but
there are only two levels: a subprole cannot have further
sub-subproles.
The AppArmor ChangeHat feature can be used by applica-
tions to access hats or subproles during execution. Current-
ly the packages apache2-mod_apparmor and tom-
3
cat_apparmor utilize ChangeHat to provide sub-process
connement for the Apache Web server and the Tomcat
servlet container.
Helpful Additions
Autodocumentation
The tool “sitar” gathers all system conguration information
available from your system and creates comprehensive
system documentation. It can be used to document all new
and changed proles.
Logging and Auditing
All AppArmor events are logged using the system's audit
interface (the auditd logging to /var/log/audit/audit
.log). On top of this infrastructure, event notication can
be congured. Congure this feature using YaST. It is based
on severity levels according to /etc/apparmor/
severity.db. Notication frequency and type of noti-
cation (such as e-mail) can be congured.
If auditd is not running, AppArmor logs to the system log
located under /var/log/messages using the LOG_KERN
facility.
Use YaST for generating reports in CSV or HTML format.
Directories and Files
/sys/kernel/security/apparmor/profiles
Virtualized le representing the currently loaded set of
proles.
/etc/apparmor/
Location of AppArmor conguration les.
/etc/apparmor.d/
Location of proles, named with the convention of re-
placing the /in pathnames with .(not for the root /)
so proles are easier to manage. For example, the prole
for the program /usr/sbin/ntpd is named usr.sbin
.ntpd.
/etc/apparmor.d/abstractions/
Location of abstractions.
/etc/apparmor.d/program-chunks/
Location of program chunks.
/proc/*/attr/current
Review the connement status of a process and the
prole that is used to conne the process. The ps auxZ
command retrieves this information automatically.
For More Information
To learn more about the AppArmor project, check out the
project's home page under http://en.opensuse.org/
AppArmor. Find more information on the concept and the
conguration of AppArmor in the Novell AppArmor Admin-
istration Guide.
Legal Notice
Copyright© 2006-2008 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the
express written consent of the publisher. For Novell trade-
marks, see the Novell Trademark and Service Mark list
[http://www.novell.com/company/legal/
trademarks/tmlist.html]. All third-party trademarks
are the property of their respective owners. A trademark
symbol (® , ™, etc.) denotes a Novell trademark; an asterisk
(*) denotes a third-party trademark.
4
Created by SUSE® with XSL-FO
5
Autres manuels pour APPARMOR - AND
3
Ce manuel convient aux modèles suivants
1
Table des matières
Autres manuels Novell Logiciel
Novell
Novell OPEN ENTERPRISE SERVER - CONVERSION GUIDE... Manuel utilisateur
Novell
Novell LINUX ENTERPRISE SERVER 10 SP1 - ARCHITECTURE-SPECIFIC INFORMATION... Manuel
Novell
Novell GROUPWISE 7 - CROSS-PLATFORM Manuel utilisateur
Novell
Novell IMANAGER 2.7.3 Manuel utilisateur
Novell
Novell OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR... Manuel utilisateur
Novell
Novell SENTINEL 6.1 SP2 - INSTALLATION GUIDE... Manuel utilisateur
Novell
Novell GROUPWISE 8 - DATABASES Manuel utilisateur
Novell
Novell IDENTITY MANAGER 3.6.1 - WORKORDER DRIVER IMPLEMENTATION GUIDE... Manuel utilisateur
Novell
Novell OPEN ENTERPRISE SERVER 2 SP2 - PLANING AND IMPLEMENTATION GUIDE... Manuel utilisateur
Novell
Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 Manuel utilisateur
Novell
Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE... Guide de référence rapide
Novell
Novell SERVER CONSOLIDATION MIGRATION TOOLKIT 1.2 - ADMINISTRATION GUIDE... Mode d’emploi
Novell
Novell GROUPWISE 8 - DOMAINS Manuel utilisateur
Novell
Novell DATA SYNCHRONIZER - 07-2010 Mode d’emploi
Novell
Novell IMANAGER 2.7.3 - README 8-26-2010 Manuel utilisateur
Novell
Novell EDIRECTORY 8.8 SP5 Mode d’emploi
Novell
Novell LINUX ENTERPRISE SERVER 11 - DEPLOYMENT Guide de référence rapide
Novell
Novell LINUX ENTERPRISE DESKTOP 10 SP1 - START UP GUIDE... Manuel utilisateur
Novell
Novell ZENWORKS ENDPOINT SECURITY MANAGEMENT 3.5 Mode d’emploi
Novell
Novell LINUX ENTERPRISE SERVER 11 - VIRTUALIZATION Manuel utilisateur
Manuels Logiciel populaires d'autres marques
Canon
Canon Vixia HF21 Manuel utilisateur
Canon
Canon ZR950 Manuel utilisateur
Samsung
Samsung Auto Backup Manuel utilisateur
Polycom
Polycom Vortex EF2201 Instructions d'installation et d'utilisation
Brocade Communications Systems
Brocade Communications Systems Brocade 8/12c Manuel utilisateur
Lexmark
Lexmark Apps Manuel de service