111
Chapter 6: Secure SSH Tunneling & SDT Connector
o IfyouareconnectingasaUserinthe“users”groupthenyoucanonlySSHtunneltoHostsandSerialPorts
where you have specific access permissions
o IfyouareconnectingasanAdministrator(inthe“admin”group)thenyoucanconnecttoanyconguredHostor
SerialPorts(which has SDT enabled)
TosetupthesecureSSHtunnelforaHTTPbrowserconnectiontotheManagedDevicespecifyport80(ratherthanport3389
aswasusedforRDP)intheDestinationIPaddress.
TosetupthesecureSSHtunnelfromtheClient(Viewer)PCtotheConsoleServerforVNCfollowthestepsabove,however
whenconguringtheVNCportredirectionspecifyport5900intheDestinationIPaddress.
Note:HowsecureisVNC?VNCaccessgenerallyallowsaccesstoyourwholecomputer,sosecurityisveryimportant.VNC
uses a random challenge-response system to provide the basic authentication that allows you to connect to a VNC server. This
is reasonably secure and the password is not sent over the network.
However, once connected, all subsequent VNC traffic is unencrypted. So a malicious user could snoop your VNC session. Also
there are VNC scanning programs available, which will scan a subnet looking for PCs which are listening on one of the ports
which VNC uses.
Tunneling VNC over a SSH connection ensures all traffic is strongly encrypted. Also no VNC port is ever open to the internet, so
anyone scanning for open VNC ports will not be able to find your computers. When tunneling VNC over a SSH connection, the
only port which you're opening on your Console Server the SDT port 22.
So sometimes it may be prudent to tunnel VNC through SSH even when the Viewer PC and the Console Server are both on the
same local network.