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>
This commit is contained in:
Simon McVittie 2018-04-23 18:27:25 +01:00
parent d0a16b59a8
commit 3aa8bff8e2

View file

@ -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