[4.1] 9c7f0d5 Reword
Federico G. Schwindt
fgsch at lodoss.net
Fri Sep 4 15:54:50 CEST 2015
Author: Federico G. Schwindt <fgsch at lodoss.net>
Date: Fri Jul 10 17:25:25 2015 +0100
Partially from minusf via github
diff --git a/doc/sphinx/users-guide/run_security.rst b/doc/sphinx/users-guide/run_security.rst
index 5b9dfad..d83ea18 100644
@@ -65,10 +65,10 @@ memory.
By using a "localhost" address, you restrict CLI access
to the local machine.
-You can also bind the CLI port to an IP number reachable across
+You can also bind the CLI port to an IP address reachable across
the net, and let other machines connect directly.
-This gives you no secrecy, ie, the CLI commands will
+This gives you no secrecy, i.e. the CLI commands will
go across the network as ASCII text with no encryption, but
the -S/PSK authentication requires the remote end to know
the shared secret.
@@ -88,10 +88,8 @@ to your central Varnish management facility.
.. XXX:Maybe a sample command here with a brief explanation? benc
-The connection is also in this case without secrecy, but
-the remote end must still satisfy -S/PSK authentication.
-.. XXX:Without encryption instead of secrecy? benc
+The connection in this case is also without encryption, but
+the remote end must still authenticate using -S/PSK.
Finally, if you run varnishd with the '-d' option, you get a CLI
command on stdin/stdout, but since you started the process, it
More information about the varnish-commit