Add Audit control to AppArmor through, the use of audit and deny

key words.  Deny is also used to subtract permissions from the
profiles permission set.

the audit key word can be prepended to any file, network, or capability
rule, to force a selective audit when that rule is matched.  Audit
permissions accumulate just like standard permissions.

  eg.
  audit /bin/foo rw,

  will force an audit message when the file /bin/foo is opened for
  read or write.

  audit /etc/shadow w,
  /etc/shadow r,
  will force an audit message when /etc/shadow is opened for writing.
  The audit message is per permission bit so only opening the file
  for read access will not, force an audit message.

  audit can also be used in block form instead of prepending audit
  to every rule.

  audit {
    /bin/foo rw,
    /etc/shadow w,
  }
  /etc/shadow r,	# don't audit r access to /etc/shadow


the deny key word can be prepended to file, network and capability
rules, to result in a denial of permissions when matching that rule.
The deny rule specifically does 3 things
- it gives AppArmor the ability to remember what has been denied
  so that the tools don't prompt for what has been denied in
  previous profiling sessions.
- it subtracts globally from the allowed permissions.  Deny permissions
  accumulate in the the deny set just as allow permissions accumulate
  then, the deny set is subtracted from the allow set.
- it quiets known rejects.  The default audit behavior of deny rules
  is to quiet known rejects so that audit logs are not flooded
  with already known rejects.  To have known rejects logged prepend
  the audit keyword to the deny rule.  Deny rules do not have a
  block form.

eg.
  deny /foo/bar rw,
  audit deny /etc/shadow w,

  audit {
     deny owner /blah w,
     deny other /foo w,
     deny /etc/shadow w,
  }

parser/parser_misc.c

@@ -62,7 +62,11 @@ static struct keyword_table keyword_table[] = {
 	{"unsafe",		TOK_UNSAFE},
 	{"link",		TOK_LINK},
 	{"owner",		TOK_OWNER},
+	{"user",		TOK_OWNER},
+	{"other",		TOK_OTHER},
 	{"subset",		TOK_SUBSET},
+	{"audit",		TOK_AUDIT},
+	{"deny",		TOK_DENY},
 	/* terminate */
 	{NULL, 0}
 };
@@ -520,8 +524,11 @@ reeval:
 			break;
 
 		case COD_EXEC_CHAR:
-			PDEBUG("Parsing mode: found %s EXEC\n", mode_desc);
-			yyerror(_("Invalid mode, 'x' must be preceded by exec qualifier 'i', 'p', or 'u'"));
+			/* this is valid for deny rules, and named transitions
+			 * but invalid for regular x transitions
+			 * sort it out later.
+			 */
+			mode |= AA_MAY_EXEC;
 			break;
 
  		/* error cases */
@@ -572,7 +579,7 @@ struct cod_entry *new_entry(char *namespace, char *id, int mode, char *link_id)
 {
 	struct cod_entry *entry = NULL;
 
-	entry = (struct cod_entry *)malloc(sizeof(struct cod_entry));
+	entry = (struct cod_entry *)calloc(1, sizeof(struct cod_entry));
 	if (!entry)
 		return NULL;
 
@@ -580,6 +587,7 @@ struct cod_entry *new_entry(char *namespace, char *id, int mode, char *link_id)
 	entry->name = id;
 	entry->link_name = link_id;
 	entry->mode = mode;
+	entry->audit = 0;
 	entry->deny = FALSE;
 
 	entry->pattern_type = ePatternInvalid;
@@ -596,7 +604,7 @@ struct cod_entry *copy_cod_entry(struct cod_entry *orig)
 {
 	struct cod_entry *entry = NULL;
 
-	entry = (struct cod_entry *)malloc(sizeof(struct cod_entry));
+	entry = (struct cod_entry *)calloc(1, sizeof(struct cod_entry));
 	if (!entry)
 		return NULL;