On 2014-12-02 13:48, DRC wrote:
>
> As far as transmitting over HTTPS, it's not as simple as just using a
> different client. You'd need a proxy on the server end as well,
> something that could intercept the HTTPS connections and farm them out
> to the appropriate VNC server instances. We support the UltraVNC
> Repeater, which will allow you to use a single port on the server for
> all VNC connections, but it doesn't use HTTPS. It is still using the
> RFB protocol.
>
How about WebSockets? Do you see any potential issues with this?
1. TurboVNC Applet modifications
Modify TurboVNC Applet to connect using encrypted WebSockets
(wss://).
2. Apache 2.4 + mod_proxy_wstunnel
(http://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html)
This would proxy the wss:// connection received at the webserver
to a backend websocket server.
3. Websockify
(https://github.com/kanaka/websockify)
This would proxy the data between the websocket connection and the
actual VNC server.
Thanks,
Dyweni
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
TurboVNC-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/turbovnc-users
