Why do the files /etc/selinux/policyname/policy/policy. and /etc/selinux/policyname/src/policy/policy. have different (sizes, md5sums, dates)?
When you install a policy package, pre-compiled binary policy files are put directly into /etc/selinux. When a policy source package is installed or updated, binary policy files are built in /etc/selinux/policyname/src/policy, then moved to /etc/selinux/policyname/policy/. The different build environments will make target files that have different sizes, md5sums, and dates.
Related Questions
- The MD5 Sums for My Policy/Config/Tripwire Executable Files at Installation are different than what my Latest Report tells me. How could this happen?
- Why do binary policies distributed with Fedora, such as /etc/selinux//policy/policy., and those I compile myself have different sizes and MD5 checksums?
- Can I transfer database or simulation files between different versions of Policy Insight?
