Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I don't think that your initial statement is correct. A computer or terminal needs to have the x11r6 server running to be able to display the output on the screen. Also, without even a simple window manager, you will not have borders or menus displayed. ( I am referring to computer S now. ) The role of server/client is different than what many expect. The X11 server is what displays things on the screen, so it is the terminal machine running the server. The program running on the different machine is the client. Techically, both may need the server program running, but the remote machine doesn't need a window manager if it doesn't display anything.
There are security policies which may control the usage of xauth. Try reading /usr/share/doc/packages/pam/README.pam_xauth as well as the xauth man and info pages.
There is also a readme on x-windows access in the www.tldp.org web site. The NSA site has an x-windows security how-to that you could probably find using google.
You need to read up on how your system controls this. For many distro's the use of xauth is controlled by PAM. I already refered to the readme document for this. Other distro's such as Slackware do not use PAM. Here you would need to manually merge the magic cookie from ~/.Xauthority on host L to the ~/.Xauthority on host S.
A user's .Xauthority file is only readable by the owner.
A better way may be to use ssh with x-forwarding. The handing of the X-auth cookies and setting of $DISPLAY is handled in the background. I've only used ssh to run programs remotely. I have rarely pushed an output like that. I think I just did it once as an experiment. However, I've used ssh on my laptop to run a program on my desktop, while displaying the program on the laptop.
If you also want sound to be played on the remote rather than the local machine, there may be more work and setup for this.
You may have better luck following these instructions. I don't think you are transfering the cookie information from the S host to the L host. http://acs.ucsd.edu/info/xauth.php
Giving another machine access
Set up .rhosts
To allow connections from another machine, first set up an .rhosts file on the remote machine. You've probably already done this before even thinking about figuring out xauth, but it's still important. The .rhosts file should contain the name of the local machine and your username on one line, separated by a space. This is the same file that you use to enable rsh, rlogin, and rcp. For more information on .rhosts files, see "help rcp".
Transfer the cookie
To transfer the cookie to a remote machine, set up the .rhosts file on that machine as described above, then type (replacing "remote" with the name of the remote machine you want to use):