xpra icon
Bug tracker and wiki

Changes between Version 17 and Version 18 of Encryption/SSL


Ignore:
Timestamp:
10/12/19 12:49:05 (5 weeks ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Encryption/SSL

    v17 v18  
    77
    88For more details see #1252.
     9
     10The TCP to SSL socket upgrade can be used with SSL clients, websockets clients (html5 clients) or HTTPS connections.
    911
    1012This option can more easily go through some firewalls and may be required by some network policies. Client certificates can also be used for authentication.
     
    4042xpra attach ssl://127.0.0.1:10001/
    4143}}}
    42 }}}
    43 
    44 
    45 {{{#!div class="box"
    46 == SSL Mode ==
    47 
    48 The TCP to SSL socket upgrade can be used with SSL clients, websockets clients (html5 clients) or HTTPS connections.
    49 
    50 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)
    51 With older versions, the option {{{ssl=MODE}}} can be used to select which client protocols will be allowed on the {{{bind-tcp}}} sockets:
    52 ||= Mode  =||||||= Client Protocol =||
    53 || ||= SSL =||= Websockets =||= Secure Websockets =||
    54 ||auto [[BR]](default)|| Yes || Yes || No ||
    55 ||TCP|| Yes || No || No ||
    56 ||www|| No || Yes || Yes ||
    5744}}}
    5845
     
    158145}}}
    159146
    160 Starting with version 2.4 (r20175), the cadata can also be encoded using base64:
     147The cadata can also be encoded using base64, which more dense:
    161148{{{
    162149python -c "import sys,base64;print(base64.b64encode(open(sys.argv[1]).read()))" ca.crt