Books for you

tightvnc.com/">TightVNC site

4. You can now access the Java applet page at http://blue/vnc/ (adjust the URI if
you placed the VNC directory in a location other than the DocumentRoot).
14.12 Accessing VNC Securely Using SSH
VNC addresses two of the three remote access challenges (Section 13.7): access control
and network bandwidth and latency. It doesn??™t protect your data in transit,
although it does avoid sending VNC passwords in plain text across the network.
To use VNC securely, it is necessary to add an encryption layer. There are several
ways to do this, but the most common is to tunnel the RFB protocol through an SSH
tunnel.
Most binary VNC viewers can automatically start an SSH client to create a tunnel.
This is done with the -via argument:
green$ vncviewer -via user@blue localhost:40
vncviewer will launch ssh with the appropriate arguments to log in to blue with the
user ID vncuser and open a pipe from green to blue. The VNC server contacted is
specified as localhost:40, but since that is written from the perspective of the remote
end of the connection, localhost refers to the host blue.
14.13
206 Chapter 14: Using VNC
The standard Java viewers do not provide SSH tunneling capability.


Pages:
298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322