sc_exit implies sc_prompt?

[mmegumi]

I have used UltraVNC server 1.0.8.2 successfully with various non-UltraVNC clients and mostly for reverse connections. Typical usage in these cases:

$ winvnc.exe -sc_exit -connect <ip::port> -run

Using the same ultravnc.ini and winvnc.exe 1.0.9.6.1, this command line causes connection errors with some non-UltraVNC clients in listen mode; e.g.:

TigerVNC 1.0.90: "CConnection: No matching security types"
Remmina (based on LibVNCServer/LibVNCClient 0.97): "Unknown authentication scheme from VNC server: -1294303224"
UltraVNC 1.0.9.6.1: prompts to confirm connection

In fact, by adding -sc_prompt as the first command line parameter to winvnc.exe, connection behavior does not change with any of these clients. This is not true of winvnc.exe 1.0.8.2.

Using winvnc.exe 1.0.9.6.1, is it possible to have -sc_exit without -sc_prompt behaviour?

[YY]

Typical usage in these cases:

$ winvnc.exe -sc_exit -connect <ip::port> -run

............................

UltraVNC 1.0.9.6.1: prompts to confirm connection

I can repeat this bug. The "-sc_exit" always triggers the "-sc_prompt" in 10961.

This dosen't happen on 1.0.8.2 or before.