[KLUG Members] RE: vnc and ssh tunneling...

[Robert V. Kanaley]

Mark,

Just 'cause I am a suspenders and belt kinda admin, I have to ask. Did you
do a port scan from work to make sure that when you manually started up the
VNC server on your home machine that your firewall at home was blocking the
listening VNC ports at 58XX and 59XX?

SSH tunneling works great to secure VNC connections, but for any machines
exposed to the Internet, you have to be sure to use the firewall to restrict
access to the VNC ports to localhost, via your SSH tunnel, only.

Incidentally, if you want to remotely connect to your running X desktop at
home instead of having to startup a second X desktop with Xvnc (VNC Server),
I presume you can do the same thing in SuSE 10 that I do in SuSE 9. I use
the SuSE Control Center, Internet and Network, Desktop Sharing applet to
configure desktop sharing so that you can connect to your running desktop at
home using just a password. By default, Desktop Sharing requires local
confirmation in addition to the password, before a remote host is allowed to
connect to the running desktop. If you are securely logging in to your home
desktop from work, you wouldn't be at home to confirm that you want to allow
the remote connection.

Regards,

Bob

Robert V. Kanaley
Manager Information Systems
Agdia, Inc.
rvk at agdia.com
http://www.agdia.com


>i have a suse 10.0 box running sshd (all the time on port 22) and
>vncserver (manually started on
>occasion). i want to be able to vnc into my box at home from work
>(using my windows xp workstation
>and tightvnc). i want to do this securely via ssh. what are the
>proper steps to use ssh tunneling?
>and talk slowly if you know what i mean.
>
>thank-you
>
>--
>Mark Bystry
>SuSE 10.0
>KDE 3.4.2
>
>