diff options
| author | Frank Osterfeld <frank@kdab.net> | 2009-06-09 11:56:38 +0200 |
|---|---|---|
| committer | Ralf Habacker <ralf.habacker@freenet.de> | 2009-12-01 08:43:40 +0100 |
| commit | 5012769a3f9142c18303c2d2fda61b4406548403 (patch) | |
| tree | 23286fbb087838595433d109adf06ac150832d8e /doc | |
| parent | b0091cf47e1172b1d5c1b0c060efe8b60c3b11e1 (diff) | |
| download | dbus-5012769a3f9142c18303c2d2fda61b4406548403.tar.gz | |
Add nonce-tcp section to the specification (draft) (cherry picked from commit 7015b2db6c8744c88da9cb0fab8d5e0fcfc0220b)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/dbus-specification.xml | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index fc2caffd..be9c9ffb 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -2426,6 +2426,39 @@ would be padded by Nul bytes. </para> </sect2> + <sect2 id="transports-nonce-tcp-sockets"> + <title>Nonce-secured TCP Sockets</title> + <para> + The nonce-tcp transport provides a secured TCP transport, using a + simple authentication mechanism to ensure that only clients with read + access to a certain location in the filesystem can connect to the server. + The server writes a secret, the nonce, to a file and an incoming client + connection is only accepted if the client sends the nonce right after + the connect. The nonce mechanism requires no setup and is orthogonal to + the higher-level authentication mechanisms described in the + Authentication section. + </para> + + <para> + On start, the server generates a random 16 byte nonce and writes it + to a file in the user's temporary directory. The nonce file location + is published as part of the server's D-Bus address using the + "noncefile" key-value pair. + + After an accept, the server reads 16 bytes from the socket. If the + read bytes do not match the nonce stored in the nonce file, the + server MUST immediately drop the connection. + If the nonce match the received byte sequence, the client is accepted + and the transport behaves like an unsecured tcp transport. + </para> + <para> + After a successful connect to the server socket, the client MUST read + the nonce from the file published by the server via the noncefile= + key-value pair and send it over the socket. After that, the + transport behaves like an unsecured tcp transport. + </para> + </sect2> + </sect1> <sect1 id="naming-conventions"> |