X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=INSTALL.SSL;h=061af97ab1ba010f6b7bc50e51a45892f5c508af;hb=28c5588e8e1a8d091c5d2275232c35f2968a97fa;hp=f322b41315bfef638b9a513d19027204862b0a18;hpb=f272ec7373a11a5917c9f3aca56969a48eec2f96;p=sliver-openvswitch.git

diff --git a/INSTALL.SSL b/INSTALL.SSL
index f322b4131..061af97ab 100644
--- a/INSTALL.SSL
+++ b/INSTALL.SSL
@@ -7,8 +7,8 @@ with OpenSSL.  SSL support ensures integrity and confidentiality of
 the OpenFlow connections, increasing network security.
 
 This file explains how to configure an Open vSwitch to connect to an
-OpenFlow controller over SSL.  Refer to INSTALL.Linux for instructions
-on building Open vSwitch with SSL support.
+OpenFlow controller over SSL.  Refer to INSTALL for instructions on
+building Open vSwitch with SSL support.
 
 Open vSwitch uses TLS version 1.0 or later (TLSv1), as specified by
 RFC 2246, which is very similar to SSL version 3.0.  TLSv1 was
@@ -115,7 +115,7 @@ that contains the PKI structure:
       % ovs-pki req+sign ctl controller
 
 ctl-privkey.pem and ctl-cert.pem would need to be copied to the
-controller for its use at runtime.  If you were to use ovs-controller,
+controller for its use at runtime.  If you were to use test-controller,
 the simple OpenFlow controller included with Open vSwitch, then the
 --private-key and --certificate options, respectively, would point to
 these files.
@@ -306,10 +306,6 @@ After you have added all of these configuration keys, you may specify
 "tcp:" connection methods are still allowed even after SSL has been
 configured, so for security you should use only "ssl:" connections.
 
-Unlike most Open vSwitch settings, the SSL settings are read only
-once, at ovs-vswitchd startup time.  For changes to take effect,
-ovs-vswitchd must be killed and restarted.
-
 Reporting Bugs
 --------------