Does not work with TightVNC 2.7.10

[macmacy]

My config:

• server: TightVNC 2.7.10 at Windows XP
• viewer: TightVNC 2.7.10 at Windows 7
• rfbproxy at Ubuntu 12.04 (also tried at Mac OS X - same result)

Direct connection between server and viewer works fine (with and without authentication).
I start rfbproxy like this:

./rfbproxy --record --server 192.168.203.76:0 20376.log -v

But rfbproxy gives the following output when trying to connect to server:

Authentication type 16 not understood

It behaves the same, no matter if authentication is enabled or disabled at server.

[sdaau]

I've just tried rfbproxy, and it seems I have the same problem: server is Windows 10 TightVNC server, rfbproxy runs on Ubuntu Linux 20.04 (built from source) - and, I use ssvncviewer on the Ubuntu machine itself to connect to rfbproxy - and I too get "Authentication type 16 not understood".

Just wanted to note, that I stumbled upon https://fossies.org/linux/ssvnc_no_windows/src/patches/tight-vncviewer-full.patch, and realized that ssvncviewer recognizes an environment variable SSVNC_SET_SECURITY_TYPE, whose value is a number that should be set to type of authentication: 0 is NoAuth, 1 is VncAuth (cannot find a list for the others).

In the rfbproxy source, rfbproxy.c says:

        if (auth > 2) {
                fprintf(stderr, "Authentication type %d not understood\n",
                        auth);
        }

... means it does not recognize anything else but NoAuth and VncAuth.

So I tried calling my ssvncviewer like so, to connect to rfbproxy

$ SSVNC_SET_SECURITY_TYPE=2 ssvncviewer 127.0.0.1:10
Proto: RFB 003.008

Connected to RFB server, using protocol version 3.8

Performing standard VNC authentication

... and it just hangs there; rfbproxy at this time does not report anything - so it seems that the Windows VNC server refuses to act on this authentication.

Oh well, it was worth a try ...

[Kreijstal]

correct it seems someone needs to implement the authentication mechanisms!