From 19f6901c9a054e679a514c6912449d70edfb3fa7 Mon Sep 17 00:00:00 2001
From: Simon McVittie <simon.mcvittie@collabora.co.uk>
Date: Fri, 11 Nov 2011 15:59:56 +0000
Subject: [PATCH 2/2] DBusTube: recommend Socket_Access_Control_Credentials

The two known Tubes implementations (Gabble and Salut) implement it
using libdbus, where it's actually easier to implement than anything
else. It'd be equally easy with GDBus, from what I can tell.
---
 spec/Channel_Type_DBus_Tube.xml |   12 +++++++++++-
 1 files changed, 11 insertions(+), 1 deletions(-)

diff --git a/spec/Channel_Type_DBus_Tube.xml b/spec/Channel_Type_DBus_Tube.xml
index 9615763..74e6595 100644
--- a/spec/Channel_Type_DBus_Tube.xml
+++ b/spec/Channel_Type_DBus_Tube.xml
@@ -174,7 +174,17 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
       <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
         <p>A list of the access control types that are supported with this channel.
         Note that only Socket_Access_Control_Localhost and
-        Socket_Access_Control_Credentials can be used with D-Bus tubes.</p>
+        Socket_Access_Control_Credentials can be used with D-Bus tubes.
+        Using Socket_Access_Control_Credentials is recommended.</p>
+
+        <tp:rationale>
+          <p>Socket_Access_Control_Credentials is easy to implement for a
+            D-Bus tube, because typical D-Bus library implementations like
+            libdbus and GDBus already have to support it to be able to
+            connect to the system or session bus, and usually enable it
+            by default; so there's typically no good reason to relax
+            access control to Localhost.</p>
+        </tp:rationale>
 
         <p>When requesting a channel with
           <tp:dbus-ref namespace="org.freedesktop.Telepathy">Connection.Interface.Requests.CreateChannel</tp:dbus-ref>,
-- 
1.7.7.2