Graphical selinux policy difference tool
sediffx [-d] [ORIGINAL_POLICY ; MODIFIED_POLICY]
sediffx allows the user to graphically inspect the semantic differences between two SELinux policies. All supported policy elements are examined.
sediffx supports loading SELinux policies in one of four formats.
A single text file containing policy source for versions 12 through 21. This file is usually named policy.conf.
A single file containing a monolithic kernel binary policy for versions 15 through 21. This file is usually named by version - for example, policy.20.
A list of policy packages each containing a loadable policy module. The first module listed must be a base module.
A single text file containing all the information needed to load a policy, usually exported by SETools graphical utilities.
Policies do not need to be the same format. If not provided sediffx will begin with no policies loaded.
Load the policies and differentiate them immediately. This option requires the user to specify the policies on the command line.
Print help information and exit.
Print version information and exit.
sediffx categorizes differences in policy elements into one of three forms.
The element exists only in the modified policy.
The element exists only in the original policy.
The element exists in both policies but its semantic meaning has changed. For example, a class is modified if one or more permissions are added or removed.
For all rules with types as their source or target, two additional forms of difference are recognized. This helps distinguish differences due to new types from differences in rules for existing types.
The rule exists only in the modified policy; furthermore, one or more of the types in the rule do not exist in the original policy.
The rule exists only in the original policy; furthermore, one or more of the types in the rule do not exist in the modified policy.
Most shells interpret the semicolon as a metacharacter, thus requiring a backslash like so: sediffx original.policy \; modified.policy
This manual page was written by Jeremy A. Mowery <[email protected]>.
Copyright(C) 2005-2007 Tresys Technology, LLC
Please report bugs via an email to [email protected].