Differences between revisions 3 and 5 (spanning 2 versions)
Revision 3 as of 2013-04-05 15:12:10
Size: 1205
Editor: ?IntRigeri
Comment: Add requirements section, learn more section, profiles sources and section titles.
Revision 5 as of 2013-04-05 15:19:33
Size: 1213
Editor: ?IntRigeri
Comment: Improve wording and typesetting.
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
See what running executable is currently confined by an AppArmor profile: See what running executables are currently confined by an AppArmor profile:
Line 35: Line 35:
 * in the `apparmor-profiles` package
 * [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=new-profile;users=apparmor@packages.debian.org|the patches, with new profiles included, that were submitted to Debian]]
 * in Ubuntu
 * in the `apparmor-profiles` package;
 * in [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=new-profile;users=apparmor@packages.debian.org|the patches, with new profiles included]], that were submitted to Debian;
 * in Ubuntu.

Requirements

A Debian 7.0 (Wheezy) or newer GNU/Linux system is required.

Install software

Install AppArmor userspace tools and some contributed profiles:

$ sudo apt-get install apparmor apparmor-profiles apparmor-utils

Enable AppArmor

Enable the AppArmor LSM:

$ sudo perl -pi -e 's,GRUB_CMDLINE_LINUX="(.*)"$,GRUB_CMDLINE_LINUX="$1 apparmor=1 security=apparmor",' /etc/default/grub
$ sudo update-grub
$ sudo reboot

Inspect the current state

See what running executables are currently confined by an AppArmor profile:

$ ps auxZ | grep -v '^unconfined'

Enable / install more profiles

Find more profiles:

Once you've dropped the new profile into /etc/apparmor.d/, use apparmor_parser(8) to insert it into the kernel.

AppArmor audit logs can be found in /var/log/kern.log.

Learn more

See the "External links" section on the main AppArmor page.