summaryrefslogtreecommitdiff
path: root/doc/dbus-specification.xml
diff options
context:
space:
mode:
authorSimon McVittie <smcv@collabora.com>2018-04-12 13:57:26 +0100
committerSimon McVittie <smcv@collabora.com>2018-04-23 18:27:44 +0100
commitcf47380641aac0e5b40694b0ae09ffb85ec4b5fc (patch)
treec5f7780adb9e009f91ef678dfefdaa12ecda8cd6 /doc/dbus-specification.xml
parent2513f84db68a9edad8558806b777ed6c284016b9 (diff)
spec, dbus-daemon(1): Recommend against remote TCP for debugging
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=106004 Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de> Reviewed-by: Philip Withnall <withnall@endlessm.com> [smcv: Add a TODO comment as suggested] Signed-off-by: Simon McVittie <smcv@collabora.com>
Diffstat (limited to 'doc/dbus-specification.xml')
-rw-r--r--doc/dbus-specification.xml10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index b60868f5..6ed317ff 100644
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -3731,6 +3731,16 @@
mechanism does not work for this transport.
</para>
<para>
+ Developers are sometimes tempted to use remote TCP as a debugging
+ tool. However, if this functionality is left enabled in finished
+ products, the result will be dangerously insecure. Instead of
+ using remote TCP, developers should <ulink
+ url="https://lists.freedesktop.org/archives/dbus/2018-April/017447.html"
+ >relay connections via Secure Shell or a similar protocol</ulink>.
+ <!-- TODO: Ideally someone would write a more formal guide to
+ remote D-Bus debugging, and we could link to that instead -->
+ </para>
+ <para>
All <literal>tcp</literal> addresses are listenable.
<literal>tcp</literal> addresses in which both
<literal>host</literal> and <literal>port</literal> are