Any performant native desktop clients for mac/windows have support for turbovnc websockets?

[Seth Nickell]

Anyone know of reasonably performant native desktop clients (particularly for mac or windows) that support the new websocket mode of turbovnc? I generally use the noVNC viewer, but there are times I'd just like a little more performance, and connecting directly to an RFB port (i.e. without the HTTPS websocket) is a no-go in my situation.

I also thought that perhaps there's a reverse version of `websockify` floating around I could use to proxy the websocket as a local socket? Not quite as slick, but any ideas in this direction appreciate too!

any ideas appreciated!

-Seth

[DRC]

I don’t understand the limitation. The WebSocket protocol just wraps the RFB protocol, for compatibility with noVNC. Is still uses the RFB port. The RFB listener detects whether the connection is from a WebSocket-enabled viewer or a regular VNC viewer and automatically activates the WebSocket wrapper if necessary.

If you cannot use the RFB port at all, then I don’t understand how you can use the WebSocket protocol. But you can always use the TurboVNC Viewer with SSH tunneling, which avoids any direct connections to the RFB port. If that isn’t an option, then you need to help me understand why.

On May 29, 2021, at 10:21 PM, Seth Nickell <se...@ceresimaging.net> wrote:

Anyone know of reasonably performant native desktop clients (particularly for mac or windows) that support the new websocket mode of turbovnc? I generally use the noVNC viewer, but there are times I'd just like a little more performance, and connecting directly to an RFB port (i.e. without the HTTPS websocket) is a no-go in my situation.

I also thought that perhaps there's a reverse version of `websockify` floating around I could use to proxy the websocket as a local socket? Not quite as slick, but any ideas in this direction appreciate too!

any ideas appreciated!

-Seth

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/0aa6de82-0843-4c15-8220-4c73a81a7ec3n%40googlegroups.com.

[Seth Nickell]

I have an https proxy and an otherwise closed firewall+nat between my turbovnc server and my viewer, so to reach the turbovnc server, the client must use websocket/https. 

I need a native viewer which supports accessing the proxy by websocket on a URL, which will then be proxied to turbovnc's port inside the firewall.

I already use this setup, and have helped several other people with a similar constraint.

I'm using the novnc because it's the only vncviewer i know of with websocket client support. I'd love to connect with a native client, hence the question. 🤙

You received this message because you are subscribed to a topic in the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/turbovnc-users/076a-NaRl9E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/763560F6-3C47-419F-B225-C162F9AA4FE2%40virtualgl.org.

[DRC]

I honestly don’t know if open source native WebSocket client code even exists. WebSockets is intended for browser applications, so the only places I’ve seen it in client form are JavaScript+HTML 5 and WebAssembly. One of my former corporate employers had a similar type of restrictive firewall and web proxy, but they provided a SOCKS proxy for tunneling arbitrary TCP connections through it. That is the only solution of which I’m aware, other than SSH tunneling.

On May 30, 2021, at 2:44 PM, Seth Nickell <se...@ceresimaging.net> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/CAPs6%2BdLuHHUMXJPXjqiBtKeV8D0UVkgG7eR2kgGxrwzjYiq5mQ%40mail.gmail.com.

[Seth Nickell]

Not really relevant, but I've been so delighted with https://libwebsockets.org/ in another context that I have to give it a small hat tip: there's at least one rather nicely written native websocket client lib out there! I get the impression that the embedded community has found themselves at the mercy of "web client first" APIs, producing a surprisngly rich ecosystem of C HTTP/HTTPS/websocket libs

-Seth

[DRC]

If there is support for a WebSocket client in Java, then it might have potential as a TurboVNC Viewer feature, but someone would still have to pay for my labor to implement it.

Even if that happened, I don’t understand how you would interface the TurboVNC Server with your HTTPS proxy. The TurboVNC Server has a different listening port for each session, and WebSocket connections have to be made to that port.

On May 30, 2021, at 8:51 PM, Seth Nickell <se...@ceresimaging.net> wrote:

Not really relevant, but I've been so delighted with https://libwebsockets.org/ in another context that I have to give it a small hat tip: there's at least one rather nicely written native websocket client lib out there! I get the impression that the embedded community has found themselves at the mercy of "web client first" APIs, producing a surprisngly rich ecosystem of C HTTP/HTTPS/websocket libs

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/8058b5a8-eeb3-439a-b130-ffba755261c5n%40googlegroups.com.