From: Simon McVittie <smcv@collabora.com>
Date: Mon, 23 Apr 2018 17:18:31 +0000 (+0100)
Subject: spec: Note that EXTERNAL is not *completely* impossible via TCP
X-Git-Tag: dbus-1.13.4~5
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=856ad90e82dea49e52dfaa638da2b5b47d75da49;p=thirdparty%2Fdbus.git

spec: Note that EXTERNAL is not *completely* impossible via TCP

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=106004
Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: Philip Withnall <withnall@endlessm.com>
Reviewed-by: Ralf Habacker <ralf.habacker@freenet.de>
---

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 88e7d5a1f..3e02c0b78 100644
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -3729,7 +3729,10 @@
         On Windows and most Unix platforms, the TCP stack is unable to transfer
         credentials over a TCP connection, so the
         <link linkend="auth-mechanisms-external">EXTERNAL</link>
-        authentication mechanism does not work for this transport.
+        authentication mechanism does not normally work for this transport
+        (although the reference implementation of D-Bus is able to identify
+        loopback TCPv4 connections on Windows by their port number,
+        partially enabling the EXTERNAL mechanism).
         The <link linkend="auth-mechanisms-sha">DBUS_COOKIE_SHA1</link>
         mechanism is normally used instead.
       </para>