Attachment 49393 Details for Bug 39450 – [PATCH 3/5] Define eavesdropping, and document the eavesdrop match

[patch] [PATCH 3/5] Define eavesdropping, and document the eavesdrop match

0003-Define-eavesdropping-and-document-the-eavesdrop-matc.patch (text/plain), 4.36 KB, created by Simon McVittie on 2011-07-21 09:08:39 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2011-07-21 09:08:39 UTC

Size: 4.36 KB

patch

obsolete

>From 3ee7bdd638d4d695e5136ed82d34b85aa1e4076e Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Thu, 21 Jul 2011 16:43:51 +0100
>Subject: [PATCH 3/5] Define eavesdropping, and document the eavesdrop match
>
>---
> doc/dbus-specification.xml |   62 ++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 62 insertions(+), 0 deletions(-)
>
>diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
>index 2abe799..ef5fde5 100644
>--- a/doc/dbus-specification.xml
>+++ b/doc/dbus-specification.xml
>@@ -3861,6 +3861,40 @@
>       <para>
>         FIXME 
>       </para>
>+
>+      <sect3 id="message-bus-routing-eavesdropping">
>+        <title>Eavesdropping</title>
>+        <para>
>+          Receiving a unicast message whose <literal>DESTINATION</literal>
>+          indicates a different recipient is called
>+          <firstterm>eavesdropping</firstterm>. On a message bus which acts as
>+          a security boundary (like the standard system bus), the security
>+          policy should usually prevent eavesdropping, since unicast messages
>+          are normally kept private and may contain security-sensitive
>+          information.
>+        </para>
>+
>+        <para>
>+          Eavesdropping is mainly useful for debugging tools, such as
>+          the <literal>dbus-monitor</literal> tool in the reference
>+          implementation of D-Bus. Tools which eavesdrop on the message bus
>+          should be careful to avoid sending a reply or error in response to
>+          messages intended for a different client.
>+        </para>
>+
>+        <para>
>+          Clients may attempt to eavesdrop by adding match rules
>+          (see <xref linkend="message-bus-routing-match-rules"/>) containing
>+          the <literal>eavesdrop='true'</literal> match. If the message bus'
>+          security policy does not allow eavesdropping, the match rule can
>+          still be added, but will not have any practical effect. For
>+          compatibility with older message bus implementations, if adding such
>+          a match rule results in an error reply, the client may fall back to
>+          adding the same rule with the <literal>eavesdrop</literal> match
>+          omitted.
>+        </para>
>+      </sect3>
>+
>       <sect3 id="message-bus-routing-match-rules">
>         <title>Match Rules</title>
>         <para>
>@@ -3877,6 +3911,12 @@
>           client regardless. As a result, match rules are mainly used to
>           receive a subset of broadcast signals.
>         </para>
>+        <para>
>+          Match rules can also be used for eavesdropping
>+          (see <xref linkend="message-bus-routing-eavesdropping"/>),
>+          if the security policy of the message bus allows it.
>+        </para>
>+        <para>
>         </para>
>         <para>
>           Match rules are added using the AddMatch bus method 
>@@ -4054,6 +4094,28 @@
>                     </para>
>                   </entry>
>                 </row>
>+                <row>
>+                  <entry><literal>eavesdrop</literal></entry>
>+                  <entry><literal>'true'</literal>, <literal>'false'</literal></entry>
>+                  <entry>Since D-Bus 1.5.UNRELEASED, match rules do not
>+                    match messages which have a <literal>DESTINATION</literal>
>+                    field unless the match rule specifically
>+                    requests this
>+                    (see <xref linkend="message-bus-routing-eavesdropping"/>)
>+                    by specifying <literal>eavesdrop='true'</literal>
>+                    in the match rule.  <literal>eavesdrop='false'</literal>
>+                    restores the default behaviour. Messages are
>+                    delivered to their <literal>DESTINATION</literal>
>+                    regardless of match rules, so this match does not
>+                    affect normal delivery of unicast messages.
>+                    If the message bus has a security policy which forbids
>+                    eavesdropping, this match may still be used without error,
>+                    but will not have any practical effect.
>+                    In older versions of D-Bus, this match was not allowed
>+                    in match rules, and all match rules behaved as if
>+                    <literal>eavesdrop='true'</literal> had been used.
>+                  </entry>
>+                </row>
>               </tbody>
>             </tgroup>
>           </informaltable>
>-- 
>1.7.5.4
>

Actions: View | Splinter Review

Attachments on bug 39450: 49391 | 49392 | 49393 | 49394 | 49395

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.