Jeff:
Heya. Some quick shameless self-promotion and then a
more useful answer. :) Kaboodle is a Windows application that
acts as a secure "wrapper" for VNC. It's free, it's GPL, but
it's in beta prototype now. Working on that. :)
On the Kaboodle webpage (http://kaboodle.sf.net) head
to the Links section. In there I've listed my favorite VNC
extras. One of them is ZVNC which is VNC enhanced with the
ZeBeDee secure-tunnel utility, built-in. If you declare this
version of VNC as "policy" for your network, I think it's a
much easier path to achieving your aim. I'm not of the opinion
that asking an average Windows user to establish an SSH tunnel
before using VNC is a reasonable request (no offense!).
-Scott
> Ok.. I have seen this topic aeveral times on this list, and each time it
> seems it has come to a somewhat unclear conclusion (at least in my
> mind). Finally, I have run into the same road block as many others, I
> have numerous VNC Servers on 'our' network and the idea of insecure
> communications across the network is really starting to 'irk' me.
>
> With the information I gain/apply here, I will write up a complete howto
> for securing VNC connections. Ok.. w/ that said, I now have to ask some
> questions..
>
> What is the 'best' most secure way to communicate w/ VNC Server on a
> network?
>
> Most of my clients are Windows users, however I use ONLY Linux and have
> many spare Linux boxen that I could use as 'middle men' if neccesary to
> port forward the SSH connection.
>
> So, basically all I'm looking to do here is find out how to secure a VNC
> connection, should I use the browser interface, ssh, etc..??
>
> Thanks
>
> Jeff
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
