Attachment 139019 Details for Bug 106004 – [3½/9] spec: Note that EXTERNAL is not *completely* impossible via TCP

[patch] [3½/9] spec: Note that EXTERNAL is not *completely* impossible via TCP

0002-spec-Note-that-EXTERNAL-is-not-completely-impossible.patch (text/plain), 1.23 KB, created by Simon McVittie on 2018-04-23 17:37:25 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2018-04-23 17:37:25 UTC

Size: 1.23 KB

patch

obsolete

>From 5648a29ef0f3edb15c0e18762177d09cb9cd43b2 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <smcv@collabora.com>
>Date: Mon, 23 Apr 2018 18:18:31 +0100
>Subject: [PATCH 2/4] spec: Note that EXTERNAL is not *completely* impossible
> via TCP
>
>Signed-off-by: Simon McVittie <smcv@collabora.com>
>---
> doc/dbus-specification.xml | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
>diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
>index 88e7d5a1..3e02c0b7 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>
>-- 
>2.17.0
>

Actions: View | Splinter Review

Attachments on bug 106004: 138787 | 138788 | 138789 | 138791 | 138792 | 138793 | 138794 | 138795 | 138796 | 139019 | 139020 | 139021

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.