Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 848860 - AVC while trying to run /usr/bin/firewall-cmd from confined libvirtd
AVC while trying to run /usr/bin/firewall-cmd from confined libvirtd
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Miroslav Grepl
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-08-16 11:43 EDT by Laine Stump
Modified: 2012-08-16 13:53 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-16 13:53:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Laine Stump 2012-08-16 11:43:20 EDT
We're trying to switch libvirt over to using firewalld rather than calling iptables and ebtables directly (firewalld is present in F17, but disabled by default; it will be enabled by default in F18). The interaction with firewalld is through that package's commandline utility, /usr/bin/firewall-cmd.

When we try to call firewall-cmd from libvirtd, we get the following AVC:

type=USER_AVC msg=audit(1345131322.154:3428): pid=0 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc:  denied  { send_msg } for msgtype=method_return dest=:1.256 spid=10350 tpid=11648 scontext=system_u:system_r:firewalld_t:s0 tcontext=system_u:system_r:virtd_t:s0-s0:c0.c1023 tclass=dbus  exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'

I've rerun in permissive mode and this is the only AVC that shows up in the audit logs, so hopefully a policy for just this one thing will permit it to run.
Comment 1 Daniel Walsh 2012-08-16 13:53:29 EDT
Fixed in selinux-policy-3.11.1-9.fc18.noarch

Note You need to log in before you can comment on or make changes to this bug.