xpra icon
Bug tracker and wiki

Changes between Version 34 and Version 35 of Usage


Ignore:
Timestamp:
07/06/18 17:23:34 (5 months ago)
Author:
Antoine Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Usage

    v34 v35  
    3434* on the server which will export the application ({{{xterm}}} in the example), start an xpra server instance on a free display of your choice ({{{:100 in the example}}}):
    3535{{{
    36 xpra start :100 --start-child=xterm
     36xpra start :100 --start=xterm
    3737}}}
    3838* then from the client, just connect to this xpra instance:
     
    6060In this case, use TCP sockets:
    6161{{{
    62 xpra start --start-child=xterm --bind-tcp=0.0.0.0:10000
     62xpra start --start=xterm --bind-tcp=0.0.0.0:10000
    6363}}}
    6464Then, assuming that the port you have chosen ({{{10000}}} in the example above) is allowed through the firewall (if any), you can connect from the client using:
     
    6767}}}
    6868
    69 Beware: by default, TCP sockets are insecure. At the very least, you should use the "{{{--password-file}}}" option to protect those sessions. For more information see the [/wiki/ProxyServer#FileAuthentication File Authentication] page for more information.
     69Beware: by default, TCP sockets are insecure. At the very least, you should use the "{{{--tcp-auth=file,filename=mypassword.txt}}}" option to protect those sessions. For more information see [/wiki/Authentication Authentication].
    7070}}}
    7171