<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Ben,<br>
<br>
Slick documentation! I feel much better now knowing that my VNC ports
are closed and now flowing through port 22. Richard<br>
<br>
Benjamin J. Weiss wrote:<br>
<blockquote type="cite"
cite="midPine.LNX.4.44.0406111426490.2699-100000@mail.birdvet.org">
<pre wrap="">On Fri, 11 Jun 2004, Mark Haney wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Yeah there are a couple of other things that I found out when I started
using it on my boxes instead of exporting X over SSH. fire up a terminal
session on your FC box in any manner you choose (ssh, telnet, etc) and run
vcnpasswd.
</pre>
</blockquote>
<pre wrap=""><!---->
It's not a good idea to use telnet. SSH is *much* better. Also, I have a
quicky howto on tunneling VNC over ssh using PuTTY.
<a class="moz-txt-link-freetext" href="http://www.benjamin.weiss.name/putty-tunnel.html">http://www.benjamin.weiss.name/putty-tunnel.html</a>
Doing it this way also means that you can keep the firewall closed to the
vnc ports and only allow ssh through. much more secure. :)
Ben
</pre>
</blockquote>
</body>
</html>