2
0
mirror of https://gitlab.com/apparmor/apparmor synced 2025-08-31 06:16:03 +00:00
Files
apparmor/parser
John Johansen 3cb147e25c [https://bugzilla.novell.com/show_bug.cgi?id=172061]
This (updated) patch to trunk adds support for Px and Ux (toggle
bprm_secure on exec) in the parser, As requested, lowercase p and u
corresponds to an unfiltered environmnet on exec, uppercase will filter
the environment.  It applies after the 'm' patch.

As a side effect, I tried to reduce the use of hardcoded characters in
the debugging statements -- there are still a few warnings that have
hard coded letters in them; not sure I can fix them all.

This version issues a warning for every unsafe ux and issues a single
warning for the first 'R', 'W', 'X', 'L', and 'I' it encounters,
except when the "-q" or "--quiet" flag , "--remove" profile flag, or
"-N" report names flags are passed.  Unfortunately, it made the logic
somewhat more convoluted.  Wordsmithing improvements welcome.
2006-08-04 17:14:49 +00:00
..
2006-05-31 22:38:30 +00:00
2006-05-31 22:38:30 +00:00
2006-07-31 20:49:33 +00:00

Package Contents
------------------
  README 		- This file.

  subdomain_parser	- This program loads the subdomain database into
			  the kernel via the sysctl(2) interface.
  subdomain.5		- Man page explaining the structure of the
			  subdomain profile file.
  change_hat.2		- Man page explaining the usage of the change_hat
			  syscall.

subdomain_parser takes all of its input from STDIN.  Thus, if you want to
use it to load a description file, you want to do something like:

	./subdomain_parser < /path/to/database/file

Of course, you can use cat, etc. to load the contents of multiple files at
the same time.

subdomain_parser allows you to add, replace, and remove definitions
through the use of command line options. The default is to add.
`subdomain_parser --help` shows what the command line options are.

You can also find more information at
<http://forge.novell.com/modules/xfmod/project/?apparmor>.

Please send all complaints, bug reports, feature requests, rants about the
software, and questions to apparmor-general@forge.novell.com. Security
issues should be directed to security@suse.de or secure@novell.com,
where we will attempt to conform to the RFP vulnerability disclosure
protocol: http://www.wiretrip.net/rfp/policy.html

The parser uses the PCRE (Perl Compatible Regular Expression) engine,
which was written by Philip Hazel and is copyright by the University
of Cambridge, England. For more information on the PCRE engine, see
<ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/>

Thanks.

-- The AppArmor development team