spec: Describe nonce-tcp as "nonce-authenticated", not "nonce-secured"

nonce-tcp isn't really any more secure than tcp, unless you are
using ANONYMOUS authentication, which should not be considered
secure in any case. Avoid the word "secured" so that people don't
get the wrong idea.

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>

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 1b8ff635ce3c812753630885c54c780cdf3109b9..8786922ddcce3dc12ee463c13e9fa36323e91772 100644 (file)
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -3817,7 +3817,7 @@
       </sect3>
     </sect2>
     <sect2 id="transports-nonce-tcp-sockets">
-      <title>Nonce-secured TCP Sockets</title>
+      <title>Nonce-authenticated TCP Sockets</title>
       <para>
         The nonce-tcp transport provides a modified TCP transport using a
         simple authentication mechanism, to ensure that only clients with read