Comment 2 for bug 1326865

Revision history for this message
John Johansen (jjohansen) wrote :

It is a policy cross consistency check, and allows for writing policy that is selective in who it will communicate with, think rild which needs assurances it is talking to only a specific set of processes, instead of having to examine every profile to ensure the send rules are correct, only the receivers policy needs to be examined.

The fix is a small update to the dhclient profile.

  signal peer=/usr/sbin/libvirtd,

or even tighter
  signal (receive) set=(term) peer=/usr/sbin/libvirtd,