Changes between Version 17 and Version 18 of Encryption/SSL

Timestamp:

10/12/19 12:49:05 (5 weeks ago)

Author:

Antoine Martin

Comment:

--

Encryption/SSL

@@ -7 +7 @@
 
 For more details see #1252.
+
+The TCP to SSL socket upgrade can be used with SSL clients, websockets clients (html5 clients) or HTTPS connections.
 
 This option can more easily go through some firewalls and may be required by some network policies. Client certificates can also be used for authentication.
@@ -40 +42 @@
 xpra attach ssl://127.0.0.1:10001/
 }}}
-}}}
-
-
-{{{#!div class="box"
-== SSL Mode ==
-
-The TCP to SSL socket upgrade can be used with SSL clients, websockets clients (html5 clients) or HTTPS connections.
-
-Unfortunately with versions older than 2.2, not all of them at the same time. (see ticket:1213#comment:5 for details - #1504 for the fix)
-With older versions, the option {{{ssl=MODE}}} can be used to select which client protocols will be allowed on the {{{bind-tcp}}} sockets:
-||= Mode  =||||||= Client Protocol =||
-|| ||= SSL =||= Websockets =||= Secure Websockets =||
-||auto [[BR]](default)|| Yes || Yes || No ||
-||TCP|| Yes || No || No ||
-||www|| No || Yes || Yes ||
 }}}
 
@@ -158 +145 @@
 }}}
 
-Starting with version 2.4 (r20175), the cadata can also be encoded using base64:
+The cadata can also be encoded using base64, which more dense:
 {{{
 python -c "import sys,base64;print(base64.b64encode(open(sys.argv[1]).read()))" ca.crt