Differences between revisions 28 and 30 (spanning 2 versions)
Revision 28 as of 2015-01-29 16:17:17
Size: 2650
Editor: UlrikeUhlig
Comment:
Revision 30 as of 2015-01-29 17:31:39
Size: 2694
Editor: UlrikeUhlig
Comment: Simplification: people are not required to manually copy profiles to /etc/apparmor.d/. and do not need to manually parse them.
Deletions are marked like this. Additions are marked like this.
Line 53: Line 53:
Once you've dropped the new profile (this is automated when installing the DebianPkg:apparmor-profiles or the DebianPkg:apparmor-profiles-extra package) into `/etc/apparmor.d/`, use [[DebianMan:8/apparmor_parser|apparmor_parser(8)]] to insert it into the kernel. !AppArmor profiles live in `/etc/apparmor.d/`. One can use [[DebianMan:8/apparmor_parser|apparmor_parser(8)]] to insert them into the kernel. This is done automatically when installing the DebianPkg:apparmor-profiles or the DebianPkg:apparmor-profiles-extra package.
Line 57: Line 57:
## cd /usr/share/doc/apparmor-profiles/extras
## cp -i *.* /etc/apparmor.d/
Line 58: Line 61:
cd /usr/share/doc/apparmor-profiles/extras
cp -i *.* /etc/apparmor.d/
Line 65: Line 66:
== Debug ==
Line 67: Line 70:
== Debug ==

P
lease read the dedicated documentation for [[AppArmor/Debug|debugging AppArmor]].
For more detailed instructions, please read the dedicated documentation for [[AppArmor/Debug|debugging AppArmor]].

Translation(s): none


Requirements

A Debian 7 "Wheezy" or newer GNU/Linux system is required.

If you are using wheezy, upgrading to systemd 204-14 from wheezy-backports is recommended, but not mandatory.

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

In the future, this should be automated, see #702030

Inspect the current state

$ sudo aa-status

will list all loaded AppArmor profiles for applications and processes and detail their status (enforced, complain, unconfined).

$ ps auxZ | grep -v '^unconfined'

will list running executables which are currently confined by an AppArmor profile.

Enable / install more profiles

Find more profiles:

AppArmor profiles live in /etc/apparmor.d/. One can use apparmor_parser(8) to insert them into the kernel. This is done automatically when installing the apparmor-profiles or the apparmor-profiles-extra package.

For example, to set all "extra" profiles (provided in the apparmor-profiles package) to complain mode (security policy is not enforced, but corresponding access violations are logged), do the following:

for f in *.* ; do aa-complain /etc/apparmor.d/$f; done

To set these profiles to enforce mode, use aa-enforce instead of aa-complain. Note that many of these profiles are not up-to-date and might break functionality in enforce mode.

Debug

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

For more detailed instructions, please read the dedicated documentation for debugging AppArmor.

Learn more

Learn more or start contributing.