On 01/28/2013 10:42 AM, Joe Zeff wrote:
And, of course, it's often what's needed.
Unless you know that one specific process is affected by the policy,
it's pretty much always better to use 'tail -f' to capture all of the
AVCs starting at the time that you begin testing in permissive mode than
to grep for a specific context.
Here, it just revealed that there's another issue with NM.
No, it didn't. We knew from the beginning that ssh was affected by the
policy, and William generated a policy that will only affect rsync.
grep didn't reveal anything, it produced a module with too narrow a
scope to fix the problem.