Alexandre Mulatinho wrote: > You can do this with ssh! Just uncomment the line "ForwardX11" and > set him value with 'yes': > > ForwardX11 yes > > Then connect with ssh in the remote machine: ssh login@ip and when > you execute the program him appear in X in your machine. You can > try set DISPLAY too but after this you need to give access to remote > users with "xhost" command. If you do this: > > export DISPLAY=REMOTEIP:REMOTEDISPLAY > xhost + > > e.g. > export DISPLAY=10.220.220.10:0 > xhost + > > But i dont known if these way its correct! :D "xhost +" does nothing if the X server requires authentication, which is almost always the case nowadays. To use X remotely without using ssh's X forwarding, you need to copy the authentication credentials from the ~/.Xauthority file on the desktop system (the one running the X server) to the ~/.Xauthority file on the server (the one on which the X clients will be run). To do this, use a combination of "xauth extract" (on the desktop) and "xauth merge" (on the server). In most cases, it's easier to use ssh's X forwarding. First, sshd has to have X forwarding enabled via "X11Forwarding yes" in sshd_config. Then, you have to request it when connecting using "ssh -X" (or "ForwardX11 yes" in ssh_config). Also, the default X forwarding subjects clients to certain security restrictions, which can cause problems for some applications. In that case, you need to either use "ssh -Y" instead of "ssh -X", or add "ForwardX11Trusted yes" to ssh_config. If you use ssh's X forwarding, you don't need to manage the authentication credentials yourself; ssh will do this for you. -- Glynn Clements <glynn@xxxxxxxxxxxxxxxxxx> - To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
