mirror of
https://gitlab.com/apparmor/apparmor
synced 2025-08-31 22:35:35 +00:00
Default permission-hashing for dfa creation to on, to fix a bug
When doing permission merging in the dfa minimization phase the information about whether a rule is dominant or not has been lost so the merge of xtransitions can not be handled correctly. When two conflicting x transitions are merged the results are unpredicitable and not currently detected. So default dfa minimization to set up its initial partitions with permission hashing, this ensures that dfa states that have different xtransitions in the minimization stage will never be merged thus will not result in a conflict. x permission checking is still enforced at the dfa creation phase where the originial information is available to check whether the conflicting permissions came from exact match or re rules so that conflict resolution can be properly applied. The end result is that dfa minimization does not result in a truely minimal dfa (the minimization phase is also slightly faster). Signed-off-by: John Johansen <john.johansen@canonical.com>
This commit is contained in:
@@ -69,7 +69,7 @@ int binary_input = 0;
|
||||
int names_only = 0;
|
||||
int dump_vars = 0;
|
||||
int dump_expanded_vars = 0;
|
||||
dfaflags_t dfaflags = DFA_CONTROL_TREE_NORMAL | DFA_CONTROL_TREE_SIMPLE | DFA_CONTROL_MINIMIZE | DFA_CONTROL_MINIMIZE_HASH_TRANS;
|
||||
dfaflags_t dfaflags = DFA_CONTROL_TREE_NORMAL | DFA_CONTROL_TREE_SIMPLE | DFA_CONTROL_MINIMIZE | DFA_CONTROL_MINIMIZE_HASH_TRANS | DFA_CONTROL_MINIMIZE_HASH_PERMS;
|
||||
int conf_verbose = 0;
|
||||
int conf_quiet = 0;
|
||||
int kernel_load = 1;
|
||||
|
Reference in New Issue
Block a user