I made tests with modified viewer code which sends XK_Caps_Lock 0xFFE5. The server ignores it and no "C" char injected.
Hi! Can't reproduce with 2.8.85. Could you send the server log file to support@tightvnc.com ?
Hi! Going to fix in the next release.
Hi! We are not going to develop old TightVNC viewer. You could try Remote Ripple or MightyViewer.
Hi! We made a fix for this issue in commercial version and I will add it to open source one. DWORD WTS::getProcessSessionId(LogWriter* log) { DWORD id; ProcessIdToSessionId(GetCurrentProcessId(), &id); return id; } Several our commercial clients use "connect to RDP" mode but we don't have enough feedback and we don't understand very well what task is being solved with such a connection.
Hi! Try Remote Ripple viewer (free) or MightyViewer.
will be changed to sha256 in the next release
Hi! Please try Remote Ripple for Windows. https://remoteripple.com/ or https://mightyviewer.com/