There is a simplified SSH-Only mode (sshvnc). This is the name of the command to start it. The short name for this project is "ssvnc" for SSL/SSH VNC Viewer. RealVNC, TightVNC, UltraVNC, etc.) you select via 'Change VNC Viewer'. Via the provided SSVNC VeNCrypt bridge, VeNCrypt and ANONTLS encryption also works with any third party VNC Viewer (e.g. In addition to normal SSL, SSVNC also supports the VeNCrypt SSL/TLS and Vino/ANONTLS encryption extensions to VNC on Unix, Mac OS X, and Windows. The SSVNC Unix vncviewer can also be run without the SSVNC encryption GUI as an enhanced replacement for the xvncviewer, xtightvncviewer, etc., viewers. However, now the front-end GUI, encryption, and wrapper scripts features possibly outweigh the Unix TightVNC Viewer improvements (see the lists below to compare). The Enhanced TightVNC Viewer package started as a project to add some patches to the long neglected Unix TightVNC Viewer. SSVNC's SSH tunnel will work to any VNC Server host running sshd that you can log into. The x11vnc server has built-in SSL support, however SSVNC can make SSL encrypted VNC connections to any VNC Server if they are running an SSL tunnel, such as STUNNEL or socat, at their end. The package provides a GUI for Windows, Mac OS X, and Unix that automatically starts up an STUNNEL SSL tunnel for SSL or ssh/plink for SSH connections to any VNC server, such as x11vnc, and then launches the VNC Viewer to use the encrypted tunnel.
The Enhanced TightVNC Viewer, SSVNC, adds encryption security to VNC connections.
0 kommentar(er)
