Novell AppArmor provides a mod_apparmor module (package apache2-mod-apparmor) for the Apache program (only included in SUSE Linux Enterprise Server). This module makes the Apache Web server ChangeHat aware. Install it along with Apache.
When Apache is ChangeHat aware, it checks for the following customized Novell AppArmor security profiles in the order given for every URI request that it receives.
URI-specific hat (for example, ^phpsysinfo-dev/templates/classic/images/bar_left.gif)
DEFAULT_URI
HANDLING_UNTRUSTED_INPUT
NOTE: Apache Configuration
If you install apache2-mod-apparmor without Novell AppArmor, make sure that the Apache load module has a command in the configuration file that loads the mod_apparmor module by adding the following line to your Apache configuration file:
LoadModule change_hat_module modules/mod_change_hat.so
As with most of the Novell AppArmor tools, you can use two methods for managing ChangeHat, YaST or the command line interface. Managing ChangeHat-aware applications from the command line is much more flexible, but the process is also more complicated. Both methods allow you to manage the hats for your application and populate them with profile entries.
The following steps are a demonstration that adds hats to an Apache profile using YaST. In the
, the Novell AppArmor profiling utilities prompt you to create new hats for distinct URI requests. Choosing to create a new hat allows you to create individual profiles for each URI. You can create very tight rules for each request.If the URI that is processed does not represent significant processing or otherwise does not represent a significant security risk, safely select
to process this URI in the default hat, which is the default security profile.This example creates a new hat for the URI phpsysinfo-dev and its subsequent accesses. Using the profiling utilities, delegate what to add to this new hat. The resulting hat becomes a tight-security container that encompasses all the processing on the server that occurs when the phpsysinfo-dev URI is passed to the Apache Web server.
The URI runs the application phpsysinfo (refer to http://phpsysinfo.sourceforge.net for more information). The phpsysinfo-dev package is assumed to be installed in /srv/www/htdocs/phpsysinfo-dev in a clean (new) install of SUSE Linux Enterprise and AppArmor.
Once phpsysinfo-dev is installed, you are ready to add hats to the Apache profile. From the Novell AppArmor GUI, select .
In httpd2-prefork.
, enterClick
.Restart Apache by entering rcapache2 restart in a terminal window.
Restart any program you are profiling at this point.
Open http://localhost/phpsysinfo-dev/ in a Web browser window. The browser window should display network usage and system information.
NOTE: Data Caching
To ensure that this request is processed by the server and you do not review cached data in your browser, refresh the page. To do this, click the browser phpsysinfo-dev URI.
button to make sure that Apache processes the request for theClick aa-logprof tool, which scans the information learned in the previous step. It begins to prompt you with profile questions.
. Novell AppArmor launches theaa-logprof first prompts with phpsysinfo-dev URI was accessed. Select .
or because it noticed that theClick
.Choosing
in the previous step creates a new hat in the profile and specifies that the results of subsequent questions about the script's actions are added to the newly created hat rather than the default hat for this application.In the next screen, Novell AppArmor displays an external program that the script executed. You can specify that the program should run confined by the phpsysinfo-dev hat (choose
), confined by a separate profile (choose ), or that it should run unconfined or without any security profile (choose ). For the case of the option, a new profile is created for the program if one does not already exist.NOTE: Security Considerations
Selecting
can create a significant security hole and should be done with caution.Select /bin/bash path. This adds /bin/bash/ (accessed by Apache) to the phpsysinfo-dev hat profile with the necessary permissions.
for theClick
.The remaining questions prompt you to generate new hats and add entries to your profile and its hats. The process of adding entries to profiles is covered in detail in the Section 3.1, Adding a Profile Using the Wizard.
When all profiling questions are answered, click
to save your changes and exit the wizard.The following is an example phpsysinfo-dev hat.
Example 5-1 Example phpsysinfo-dev Hat
^phpsysinfo { #include <abstractions/base> /bin/df ix, /bin/bash ix, /dev/tty rw, /etc/SuSE-release r, /etc/fstab r, /etc/hosts r, /etc/mtab r, /proc/** r, /sbin/lspci ix, /srv/www/htdocs/sysinfo/** r, /sys/bus/pci/devices r, /sys/devices/** r, /usr/bin/who ix, /usr/share/pci.ids r, /var/log/apache2/{access,error}_log w, /var/run/utmp r, }
NOTE: Hat and Parent Profile Relationship
The profile ^phpsysinfo-dev is only valid in the context of a process running under the parent profile httpd2-prefork.
When you use the Section 3.3, Editing Profiles) or when you add a new profile using (for instructions, refer to Section 3.2, Manually Adding a Profile), you are given the option of adding hats (subprofiles) to your Novell AppArmor profiles. Add a ChangeHat subprofile from the window as in the following.
dialog (for instructions, refer toFrom the
window, click then select . The dialog box opens:Enter the name of the hat to add to the Novell AppArmor profile. The name is the URI that, when accessed, receives the permissions set in the hat.
Click
. You are returned to the screen.After adding the new hat, click
.NOTE: For More Information
For an example of an Novell AppArmor profile, refer to Section 5-1, Example phpsysinfo-dev Hat.