Attachment 132766 Details for Bug 92853 – dbus-daemon(1): Document how send_* and receive_* work in general

[patch] dbus-daemon(1): Document how send_* and receive_* work in general

0001-dbus-daemon-1-Document-how-send_-and-receive_-work-i.patch (text/plain), 2.55 KB, created by Simon McVittie on 2017-07-19 16:11:43 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2017-07-19 16:11:43 UTC

Size: 2.55 KB

patch

obsolete

>From 0e16d2112c9f320cb261ad6dfd9cb9a25c9b0802 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <smcv@collabora.com>
>Date: Wed, 19 Jul 2017 15:26:48 +0100
>Subject: [PATCH] dbus-daemon(1): Document how send_* and receive_* work in
> general
>
>Signed-off-by: Simon McVittie <smcv@collabora.com>
>
>---
>
>Correct the description of eavesdrop: it only creates a receive rule
>if there is no send_* attribute
>---
> doc/dbus-daemon.1.xml.in | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
>diff --git a/doc/dbus-daemon.1.xml.in b/doc/dbus-daemon.1.xml.in
>index dcaba484..cd967c87 100644
>--- a/doc/dbus-daemon.1.xml.in
>+++ b/doc/dbus-daemon.1.xml.in
>@@ -879,6 +879,32 @@ statements, and works just like &lt;deny&gt; but with the inverse meaning.</para
> particular action. If it matches, the action is denied (unless later
> rules in the config file allow it).</para>
> 
>+<para>
>+  Rules with one or more of the <literal>send_</literal>* family of attributes
>+  are checked in order when a connection attempts to send a message. The last
>+  rule that matches the message determines whether it may be sent.
>+  The well-known session bus normally allows sending any message.
>+  The well-known system bus normally allows sending any signal, selected
>+  method calls to the <command>dbus-daemon</command>, and exactly one
>+  reply to each previously-sent method call (either success or an error).
>+  Either of these can be overridden by configuration; on the system bus,
>+  services that will receive method calls must install configuration that
>+  allows them to do so, usually via rules of the form
>+  <literal>&lt;policy context="default"&gt;&lt;allow send_destination="&hellip;"/&gt;&lt;policy&gt;</literal>.
>+</para>
>+
>+<para>
>+  Rules with one or more of the <literal>receive_</literal>* family of
>+  attributes, or with the <literal>eavesdrop</literal> attribute and no others,
>+  are checked for each recipient of a message (there might be more than one
>+  recipient if the message is a broadcast or a connection is eavesdropping).
>+  The last rule that matches the message determines whether it may be received.
>+  The well-known session bus normally allows receiving any message, including
>+  eavesdropping. The well-known system bus normally allows receiving any
>+  message that was not eavesdropped (any unicast message addressed to the
>+  recipient, and any broadcast message).
>+</para>
>+
> <para>send_destination and receive_sender rules mean that messages may not be
> sent to or received from the *owner* of the given name, not that
> they may not be sent *to that name*. That is, if a connection
>-- 
>2.13.3
>

Actions: View | Splinter Review

Attachments on bug 92853: 119459 | 119460 | 131602 | 131603 | 131604 | 132757 | 132758 | 132759 | 132760 | 132761 | 132762 | 132763 | 132764 | 132765 | 132766 | 133096 | 133097

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.