mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 21:34:54 +03:00
a2028ae716
If a guest runs unconfined <seclabel type='none'>, but libvirtd is confined then the peer for signal can only be detected as 'unconfined'. That triggers issues like: apparmor="DENIED" operation="signal" profile="/usr/sbin/libvirtd" pid=22395 comm="libvirtd" requested_mask="send" denied_mask="send" signal=term peer="unconfined" To fix this add unconfined as an allowed peer for those operations. I discussed with the apparmor folks, right now there is no better separation to be made in this case. But there might be further down the road with "policy namespaces with scope and view control + stacking" This is more a use-case addition than a fix to the following two changes: - |
||
|---|---|---|
| .. | ||
| admin | ||
| apparmor | ||
| dominfo | ||
| dommigrate | ||
| domsuspend | ||
| domtop | ||
| hellolibvirt | ||
| lxcconvert | ||
| object-events | ||
| openauth | ||
| polkit | ||
| rename | ||
| systemtap | ||
| xml | ||
| Makefile.am | ||