Access Remote GUI Programs Using SSH Forwarding
Run GUI apps on another machine remotely through SSH.
The Magazine
Linux Journal is the premier source for how-tos, projects, product reviews, expert advice and opinions for everything Linux.
This Week's Member Giveaway
This week 5 lucky Members will receive a copy of The Official Ubuntu Server Book by Benjamin Mako Hill and Linux Journal's very own Kyle Rankin. No entry necessary. Check back here early next week to find out who the lucky Online Members are.
Comments
Root + SSH = No Go!
You really shouldn't allow root to login remotely!
That even counts double if you're using plain old password to log in!
You get much more security if you use ssh keys to login and don't allow root to log in remotely. Instead, log in as a normal user and use the command "su -" or "sudo" to become root *after* you have logged into the remote machine.
Last, but not least, don't use port 22 for ssh. Set sshd to listen to some other port > 1024.
I like it! shows that linux
I like it! shows that linux has something to say :D
The first time i ran the
The first time i ran the command it just worked.. I was really impressed. My server has a 5Mbit upload, so the performance was not bad at all..
however, the next day, and every day since i get the following error when i try the command.
(gnome-terminal:27725): Gtk-WARNING **: cannot open display:
CentOS 5.3 Final
Display Linux apps on a Windows desktop too
I found out how to make a Windows desktop display Linux apps also using the remote X display protocol a couple of weeks ago. The SSH client to use on Windows is Putty and you need to set this in X forwarding mode, and also have the Xming X server on Windows running in multiwindow mode.
If the Linux server is on a broadband connection, you will probably need to forward the SSH port to it from the router/firewall. If the server is running Ubuntu, make sure you run the command:
sudo aptitude install openssh-server
to install and run the SSH server on it too.
Oh and BTW, good idea to install denyhosts or similar on the ssh server to defeat password guessing attacks.
ssh -C server2@address -p
ssh -C server2@address -p gnome-terminalOutputs this:
Failed to contact the GConf daemon; exiting.server setup
To setup a machine to connect to with SSH forwarding simply do the following (ubuntu + SuSe:
make sure to install the package openssh-server on your distro
> vi /etc/ssh/sshd_config
and set:
X11Forwarding yes
> vi /etc/ssh/ssh_config
and set:
ForwardAgent yes
ForwardX11 yes
ForwardX11Trusted yes
> /etc/init.d/ssh restart
Your done and con connect with forwarding
I see a red arrow on the top
I see a red arrow on the top bar. Don't forget to install your updates.
Yes, this is great for LAN not so much for WAN. But for WAN, ssh to a command line is not so hard. Don't fear the command line. After the learning curve you can accomplish more in quicker time.
And yes, this is from someone who on WinXP has evolution open on a linux box and another ssh xterm shell open to control a OSX box. :)
Thats fascinating but what
Thats fascinating but what is required to get that up and running, i.e maybe instead of showing us to use a feature explain how it is setup i.e. how to enable/configure X forwarding, or am to understand that this is just a teaser?
GX
Cool
Been using !NX for some time now to get a remote X session; not quite as simple but with Debian it can be a 3 click process (using the .deb files, literally up and running in 5 minutes) once OpenSSH is installed. Great tip none the less; yes it is slow but more than enough in a bind.
local network will not work
I used a ip from a laptop on my local network with this command
( ski@ubuntu:~$ ssh -C -X ski@192.168.X.XXX )
also tried root before the @ sign.came back as
ssh: connect to host 192.168.x.xxx port 22: Connection refused
NOTE :I blocked my local ip with XXs for example only.
SSH?
Perhaps SSH isn't running on your server?
Shawn Powers is an Associate Editor for Linux Journal. You might find him chatting on the IRC channel, or Twitter
too slow
This tip is too slow for anything except local area network.
Sorta
Yes, over a WAN it is pretty painful to use an application -- but for an emergency configuration or something, it's tolerable over broadband.
Shawn Powers is an Associate Editor for Linux Journal. You might find him chatting on the IRC channel, or Twitter
Sneakiness
What you really need to show people is how to get around corporate firewalls and web filters by using linux on a home computer to act as a proxy both for HTTP/S and for DNS. The same techniques are also handy for safe web access in places like airports, hotels, and conventions.
Just a suggestion.
Post new comment