Hi,
On Sat, 1 Apr 2006, Hachem Osmani wrote:
> we are using a VncViewer client who supports tightvnc extension and
> libvncserver server but i think thince libvncserver doesn't understand
> tightvnc extension, the cursor positions and so on will not be activated
> , so can anybody tell me if there is an implementation of tightvnc
> extension in libvncserver so the client and the server can negotiate the
> security?????
There is support for some features of TightVNC. Notably, the tight
encoding. Also, we have support for security type negotiation. But we only
support few security types to-date.
> and i understood that backchannel.c has a special extension so it
> doesn't negotiate security type and authentification type .Is it
> right???
Yes, that is right. Backchannel implements a new encoding type that the
client can ask for. The handshake is complete when the server
sends the first backchannel message (which is only sent if the client asks
for it). Since that does not require any special negotiation, we don't
have an own security type.
I do not fully understand why TightVNC's file transfer needs an own
security type, but that was not my invention...
Hth,
Dscho
|