https://bugzilla.redhat.com/show_bug.cgi?id=2173178
--- Comment #10 from Steve Cossette <farchord(a)gmail.com> ---
So I'm trying to understand what's needed to go forward on this. The rpmlint
error mentions a missing allow, but the config does have an allow. This is the
content of the config file:
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<!-- Only user root can own the foo helper -->
<policy user="root">
<allow own="org.kde.kded.inotify"/>
</policy>
</busconfig>
And honestly, I'm looking at other dbus configs installed on my system, they
all largely use the same format with the almost same structure (Minus the "own"
parameter for obvious reasons).
Also, after checking out
https://dbus.freedesktop.org/doc/dbus-daemon.1.html, I
see this:
Rules with the own or own_prefix attribute are checked when a connection
attempts to own a well-known bus names. As a special case, own="*" matches any
well-known bus name. The well-known session bus normally allows any connection
to own any name, while the well-known system bus normally does not allow any
connection to own any name, except where allowed by further configuration.
System services that will own a name must install configuration that allows
them to do so, usually via rules of the form <policy
user="some-system-user"><allow own="…"/></policy>.
So I'm not sure if rpmlint's being too overzealous in this case. Also, I
installed the package and it does work on my machine.
I'm not sure what the procedure is here, is there any way we can let this pass?
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2173178