UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
if you're going to say you tried to compile it, why not say what happened? There are plenty of vnc viewer available through apt-get under ubuntu, why do you need a specific one?
I know tightvnc uses the ssh connection to tunnel. What other client does that that I could use that is native to Linux/Ubuntu repos etc?
May be i am not asking the right question here.
I need a secure VNC solution over SSH.
I have a system that i remote into and need a secure gui desktop on occasion.
I use tightvnc over putty at work in windows. Works fine.
I have putty on my Ubuntu system and that works. What I am missing is the secure VNC piece of the puzzle
there is no "secure VNC" piece. secure = ssh, vnc = vnc. The two parts have nothing in common. VNC has no idea whatsoever that it's being tunnelled over ssh, it just get's told to connect to localhost instead of the remote server. absolutely any vnc client will behave in exactly the same way. and certainly no need for putty on linux, just use standard ssh - "ssh user@server -L 5901:127.1:5901" for example.
Oh I use putty because the native ssh session takes longer to connect than a putty session does. I usually just ssh over for normal stuff but putty over for the VNC stuff.
No, VNC does not *try* to use SSH, VNC has NO IDEA it's using an ssh session to reach the end destination. As far as it knows it's connected to a VNC server on your own machine. I think, to be honest, you think that this is much more complicated than it really is. PuTTY can create SSH tunnels, OpenSSH client can open SSH tunnels etc. VNC is doing nothing even vaguely intelligent in the tunnelling solution at all.
tightvnc does compression, which the default client doesn't, AFAIK. However SSH is also compressed, so you're unlikely to see a benefit between the two on network traffic, as everything is squished anyway.
tightvnc does compression, which the default client doesn't, AFAIK. However SSH is also compressed, so you're unlikely to see a benefit between the two on network traffic, as everything is squished anyway.
ok so waht client should I load from the Ubuntu application manager?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.