Attachment 136112 Details for Bug 104224 – 4/9] spec: Document expected reply for each client-to-server auth command

[patch] 4/9] spec: Document expected reply for each client-to-server auth command

0004-spec-Document-expected-reply-for-each-client-to-serv.patch (text/plain), 2.57 KB, created by Simon McVittie on 2017-12-12 15:50:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2017-12-12 15:50:03 UTC

Size: 2.57 KB

patch

obsolete

>From 34e11b864b7e0a3aa735a29eabd5ed05357d02d6 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <smcv@collabora.com>
>Date: Tue, 12 Dec 2017 12:33:00 +0000
>Subject: [PATCH 4/9] spec: Document expected reply for each client-to-server
> auth command
>
>Client-to-server auth commands expect a reply, whereas
>server-to-client auth commands don't (the client is expected to send
>another command that is valid in the new state, but it isn't really
>a direct reply to the server-to-client command).
>
>Signed-off-by: Simon McVittie <smcv@collabora.com>
>---
> doc/dbus-specification.xml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
>diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
>index 7f09ba69..dc3e2492 100644
>--- a/doc/dbus-specification.xml
>+++ b/doc/dbus-specification.xml
>@@ -2272,6 +2272,7 @@
>       <title>AUTH command</title>
>       <para>
>         The AUTH command is sent by the client to the server.
>+        The server replies with DATA, OK or REJECTED.
>       </para>
>       <para>
>         If an AUTH command has no arguments, it is a request to list
>@@ -2305,6 +2306,7 @@
>       <title>CANCEL Command</title>
>       <para>
>         The CANCEL command is sent by the client to the server.
>+        The server replies with REJECTED.
>       </para>
>       <para>
>         At any time up to sending the BEGIN command, the client may send a
>@@ -2319,6 +2321,7 @@
>         The DATA command may come from either client or server, and simply
>         contains a hex-encoded block of data to be interpreted
>         according to the SASL mechanism in use.
>+        If sent by the client, the server replies with DATA, OK or REJECTED.
>       </para>
>       <para>
>         Some SASL mechanisms support sending an "empty string";
>@@ -2329,6 +2332,7 @@
>       <title>BEGIN Command</title>
>       <para>
>         The BEGIN command is sent by the client to the server.
>+        The server does not reply.
>       </para>
>       <para>
>         The BEGIN command acknowledges that the client has received an
>@@ -2405,6 +2409,7 @@
>       <title>ERROR Command</title>
>       <para>
>         The ERROR command can be sent in either direction.
>+        If sent by the client, the server replies with REJECTED.
>       </para>
>       <para>
>         The ERROR command indicates that either server or client did not
>@@ -2435,6 +2440,7 @@
>       <title>NEGOTIATE_UNIX_FD Command</title>
>       <para>
>         The NEGOTIATE_UNIX_FD command is sent by the client to the server.
>+        The server replies with AGREE_UNIX_FD or ERROR.
>       </para>
>       <para>
>         The NEGOTIATE_UNIX_FD command indicates that the client
>-- 
>2.15.1
>

Actions: View | Splinter Review

Attachments on bug 104224: 136109 | 136110 | 136111 | 136112 | 136113 | 136114 | 136115 | 136116 | 136117 | 136277 | 136278 | 136279 | 136280 | 136281 | 136282

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.