Dr Andrew Scott G7VAV

MBCS, MIET, Member ACM, Member IEEE

Senior Lecturer
School of Computing
and Communications

D35 InfoLab21
Lancaster University
Lancaster, LA1 4WA
United Kingdom

April 2024
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	1	2	3	4	5
6	7	8	9	10	11	12

AA-STATUS

Section: AppArmor (8)
Updated: 2010-12-20
Index Return to Main Contents

NAME

aa-status - display various information about the current AppArmor policy.

SYNOPSIS

aa-status [option]

DESCRIPTION

aa-status will report various aspects of the current state of AppArmor confinement. By default, it displays the same information as if the --verbose argument were given. A sample of what this looks like is:

  apparmor module is loaded.
  110 profiles are loaded.
  102 profiles are in enforce mode.
  8 profiles are in complain mode.
  Out of 129 processes running:
  13 processes have profiles defined.
  8 processes have profiles in enforce mode.
  5 processes have profiles in complain mode.

Other argument options are provided to report individual aspects, to support being used in scripts.

OPTIONS

aa-status accepts only one argument at a time out of:

--enabled: returns error code if AppArmor is not enabled.
--profiled: displays the number of loaded AppArmor policies.
--enforced: displays the number of loaded enforcing AppArmor policies.
--complaining: displays the number of loaded non-enforcing AppArmor policies.
--verbose: displays multiple data points about loaded AppArmor policy set (the default action if no arguments are given).
--help: displays a short usage statement.

BUGS

aa-status must be run as root to read the state of the loaded policy from the apparmor module. It uses the /proc filesystem to determine which processes are confined and so is susceptible to race conditions.

Upon exiting, aa-status will set its return value to the following values:

0: if apparmor is enabled and policy is loaded.
1: if apparmor is not enabled/loaded.
2: if apparmor is enabled but no policy is loaded.
3: if the apparmor control files aren't available under /sys/kernel/security/.
4: if the user running the script doesn't have enough privileges to read the apparmor control files.

If you find any additional bugs, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>.

for client 3.144.42.196

http://www.andrew-scott.uk/

Andrew Scott

http://www.andrew-scott.co.uk/