| subdomain_parser - loads AppArmor profiles into the kernel |
subdomain_parser - loads AppArmor profiles into the kernel
subdomain_parser [--add] [--debug] [--help] [--replace] [--remove] [--version] [--preprocess] [--Complain] [--Include n] [--base n] [--stdout]
subdomain_parser imports new subdomain.conf(5) profiles into the Linux kernel. The profiles restrict the operations available to processes as indicated by executable name.
The profiles are loaded into the Linux kernel by the subdomain_parser program, which takes its input from standard input. The input supplied to subdomain_parser should be in the format described in subdomain.conf(5).
The following are two ways you can use the subdomain parser. The first can be used to replace mutliple profiles at once. *cat /etc/subdomain.d/usr.bin.foo | subdomain_parser -r *subdomain_parser -r < /etc/subdomain.d/usr.bin.foo
Note: -r performs the same action as -a, if the profile does not already exist.
Removing and adding a profile has a different effect than does replacing one because when you replace a profile the processes that were attached to the profile
The diffferences between the following two commands should be noted:
*subdomain_parser -r < /etc/subdomain.d/usr.bin.foo When you replace a profile, the processes the original profile was attached to are protected.
*subdomain_parser -R < /etc/subdomain.d/usr.bin.foo and then subdomain_parser subdomain_parser -a < /etc/subdomain.d/usr.bin.foo When you remove, then add a profile, the processes that the original profile was attached to are no longer protected.
Prints the version number and exit.
profile(s) and incorporates any files referenced by #include directives, placing them inline into the profile so the profile becomes a large, flat file.
None known. If you find any, please report them to bugzilla at http://bugs.wirex.com.
subdomain(7), subdomain.d(5), subdomain.conf(5), and change_hat(2).
| subdomain_parser - loads AppArmor profiles into the kernel |