git://git.onelab.eu
/
sliver-openvswitch.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Merge branch 'mainstream'
[sliver-openvswitch.git]
/
INSTALL.SSL
diff --git
a/INSTALL.SSL
b/INSTALL.SSL
index
8511b69
..
061af97
100644
(file)
--- a/
INSTALL.SSL
+++ b/
INSTALL.SSL
@@
-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
% 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.
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.
"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
--------------
Reporting Bugs
--------------