Xvnc backend: does not support tight encoding when using vnc-any

[hellothere-yan]

When I use vnc-any to forward VNC sessions, I found that tight encoding is not supported. I would like to ask if it will be supported in the future,thanks a lot.

[matt335672]

Hi @hellothere-yan

I need some clarification.

Are you asking for support for the tight encoding encoding type, or the tight security type or both?

Can you be more specific about the problem you're trying to solve here?

Thanks.

[hellothere-yan]

Hi @hellothere-yan

I need some clarification.

Are you asking for support for the tight encoding encoding type, or the tight security type or both?

Can you be more specific about the problem you're trying to solve here?

Thanks.

Hi，I am using the tight encoding, which is the default encoding method used by both tight VNC and tight VNC，because my VNCserver only supports the tight encoding method,i want to connect to my VNCServer through vnc-any.

[matt335672]

Thanks for the clarification.

I can' promise you anything soon, I'm afraid. Our project is ASL licenced, and although there are VNC clients (and libraries) out there which support tightVNC encoding, all the ones I can find are licenced under the GPL. The tightvnc decoder is available (see here) but not on terms which are compatible with the ASL.

In other words, we can't simply embed an existing implementation of the tightvnc encoder in our code. That gives us two options, both of which involve significant development effort:-

• we could possibly make calls into libvncclient specifically to handle this encoding.
• we could provide a clean room implementation of the encoding.

I'm welcome to any other suggestions from anyone.