Attachment 138793 Details for Bug 106004 – 6/9] spec: Describe the security properties of nonce-tcp in terms of tcp

[patch] 6/9] spec: Describe the security properties of nonce-tcp in terms of tcp

0006-spec-Describe-the-security-properties-of-nonce-tcp-i.patch (text/plain), 2.14 KB, created by Simon McVittie on 2018-04-12 13:20:32 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2018-04-12 13:20:32 UTC

Size: 2.14 KB

patch

obsolete

>From fb38811b10dd457896289f4d677391b488e964ba Mon Sep 17 00:00:00 2001
>From: Simon McVittie <smcv@collabora.com>
>Date: Thu, 12 Apr 2018 13:59:43 +0100
>Subject: [PATCH 6/9] spec: Describe the security properties of nonce-tcp in
> terms of tcp
>
>Signed-off-by: Simon McVittie <smcv@collabora.com>
>---
> doc/dbus-specification.xml | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
>diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
>index 7f2933bf..fa285323 100644
>--- a/doc/dbus-specification.xml
>+++ b/doc/dbus-specification.xml
>@@ -3810,6 +3810,32 @@
>         the higher-level authentication mechanisms described in the
>         Authentication section.
>       </para>
>+      <para>
>+        The nonce-tcp transport is conceptually similar to a combination
>+        of the <link linkend="auth-mechanisms-sha">DBUS_COOKIE_SHA1</link>
>+        authentication mechanism and the
>+        <link linkend="transports-tcp-sockets">tcp</link> transport,
>+        and appears to have originally been implemented as a result of
>+        a misunderstanding of the SASL authentication mechanisms.
>+      </para>
>+      <para>
>+        Like the ordinary tcp transport, the nonce-tcp transport has no
>+        integrity or confidentiality protection, so it should normally
>+        only be used across the local loopback interface, for example
>+        using an address like <literal>tcp:host=127.0.0.1</literal> or
>+        <literal>tcp:host=localhost</literal>. Other uses are insecure.
>+        See <xref linkend="transports-tcp-sockets"/> for more
>+        information on situations where these transports have been used,
>+        and alternatives to these transports.
>+      </para>
>+      <para>
>+        Implementations of D-Bus on Windows operating systems normally
>+        use a nonce-tcp transport via the local loopback interface.
>+        This is because the
>+        <link linkend="transports-unix-domain-sockets">unix</link>
>+        transport, which would otherwise be recommended, is not
>+        available on these operating systems.
>+      </para>
> 
>       <para>
>         On start, the server generates a random 16 byte nonce and writes it
>-- 
>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.