Bug 91347 - [PATCH] policy: don't prevent us from receiving signals
Summary: [PATCH] policy: don't prevent us from receiving signals
Status: RESOLVED FIXED
Alias: None
Product: ModemManager
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: ModemManager bug user
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-15 12:03 UTC by David Herrmann
Modified: 2015-07-15 13:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
[PATCH] policy: don't prevent us from receiving signals (1.87 KB, text/plain)
2015-07-15 12:03 UTC, David Herrmann
Details

Description David Herrmann 2015-07-15 12:03:27 UTC
Created attachment 117135 [details]
[PATCH] policy: don't prevent us from receiving signals

Hi

By using:
    <deny send_destination="org.freedesktop.ModemManager1"/>

..we prevent anyone on the system from sending us signals, even if we subscribed to them. This is clearly not what this line intended. More importantly, we silently break mm-auth-provider-polkit, as we never receiver 'changed' signals via PolkitAuthority. Right now, this is not required by the implementation of PolkitAuthority, but ModemManager should not place restrictions on the implementation of external libraries.

So make sure we only prevent Method-Calls to be sent to us. Any other message that we didn't expect is automatically discarded by gdbus, anyway.

Without this change, debugging dbus policies constantly shows messages that Polkit couldn't send the 'changed' signal to ModemManager. This is suppressed in non-debugging mode. But it would make debugging a lot easier, if we'd avoid force-dropping those events and not clutter the debug-log.
Comment 1 Aleksander Morgado 2015-07-15 13:16:43 UTC
In git master now, thanks.
Comment 2 Jan Alexander Steffens (heftig) 2015-07-15 13:21:30 UTC
Prior discussion: https://github.com/systemd/systemd/issues/545


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.