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 88e7d5a1f091a7e9ebc1e3511bfcf56129258f44..3e02c0b785c4919bd2b5d4ffae55524f09c6b49f 100644 (file)
--- 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>