[SOLVED] Xserver in fedora 17, displaying from remote server.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The only setting for display is rc.local, this is for the display manager for oracle to match and be happy. mocha software in win is default, just listens, installed it out of necessity to a VM.
I read that Xserver listens in the 600x range, the mocha is 6000 on the win box. But no listening with fedora. That's what I believe is the issue, the fedora listening for connections. I can send display to another system from this and other servers, if it's the win box.
Completely unedited, can display xclock to the win box but not fedora by telling it where to send it.
That's not how you use X forwarding through SSH. You don't "push" the display to some random IP with a listening X server. As jpollard said:
Originally Posted by jpollard
sshd creates the X forwarding by opening a TCP port (6000+offset specified from sshd config file+increment to find unused port). That port is then passed to the X clients using the DISPLAY environment variable (value is localhost:<port-6000>.0). Any other value causes an access failure due to improper credentials.
DISPLAY should be set automatically when you run ssh -X (or ssh -Y) to localhost:<port-6000>.0. You do not force it to anything. You mentioned that rc.local is modifying display, how so? An example of how it should look:
Maybe this is one thing that I'm trying to say, I'm not trying to use ssh as the vehicle. All the years (few beit) that I've been in Linux, I've always connected via ssh, exported display to a host (windows w/ X software) and sent the display back to myself. I wanted to ask at large how to use the same functionality within Linux to send the display back, it was the original desire to continue working it the same way.
Yes, I can ssh to localhost and run, but I have the desire to get out of windows. I can make a Linux node display to windows host, but not back to another Linux host.
Well unfortunately you've been doing it wrong. The way you've been working is insecure, error-prone, labor-intensive, and only works when connecting between machines on the same local network or when you have a public IP. Perhaps instead of trying to force Linux to do it the wrong way, you should start learning how to do it the right way?
Since the X connection works properly when you ssh to yourself, that means you're using it correctly. So again, the problem comes down to a misconfiguration on the server.
Besides being insecure, the configuration and use of the display manager disable TCP connections because it is insecure.
X by default doesn't use TCP.
And until the use of encrypted TCP based X connections is restored (I believe it is being worked on), X will remain insecure over TCP. It passes the connection authorization in plaintext, and the usual authorization is just an long password, so it is as bad as using unencrypted passwords anywhere else.
OK, well, I didn't know that it was insecure. I can see with public access how that can be, yes. But it's all internal. It's worked well for years, just exporting out to send the display out if you needed a GUI on a run-level 3 box. Nothing much really to it.
Yes, if there is a better way, I'm all for it. I'm not seasoned on Linux, converted win guy... But I do learn regularly.
Thanks everyone for banging me through it. It is greatly appreciated.