From c1c9ecaa8a3d6a23fa9eae71d37eafacb9c9b975 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Thu, 12 Apr 2018 13:57:26 +0100 Subject: [PATCH] dbus-daemon(1): Recommend against remote TCP for debugging Bug: https://bugs.freedesktop.org/show_bug.cgi?id=106004 Reviewed-by: Ralf Habacker Reviewed-by: Philip Withnall [smcv: Add a TODO comment as suggested] Signed-off-by: Simon McVittie (cherry picked from commit cf47380641aac0e5b40694b0ae09ffb85ec4b5fc) --- doc/dbus-daemon.1.xml.in | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/dbus-daemon.1.xml.in b/doc/dbus-daemon.1.xml.in index 891fbfb0f..094389dfc 100644 --- a/doc/dbus-daemon.1.xml.in +++ b/doc/dbus-daemon.1.xml.in @@ -415,6 +415,16 @@ a transport name plus possible parameters/options. configuring the well-known system bus or the well-known session bus to listen on a non-loopback TCP address is insecure. + + 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 relay connections via Secure Shell or a similar protocol. + + Example: <listen>unix:path=/tmp/foo</listen> -- 2.47.3