Re: [SLE] need help with X11 security

Thanks for the reply. I should have been more explicit. The X client is an existing, old (non-linux) software installation which doesn't use the latest security features of X11, so I need to "back off" the security requirements on the SLES 10 box. I am not trying to do a remote terminal, or login a particular user, or anthing of that kind. Basically, it just exports its GUI to the SLES 10 box. As I said, it worked fine with the settings below until Beta 3, or 4. Does anyone know what changed?

...

...

Joseph Loo 02/24/06 8:39 PM >>> I prefer a different method to secure the box. Fisrt I do not allow telnet or rlogin (I think). I also have ftp, rcp, etc. turned off. These services are all turned off. When I want to connect to the box, I use ssh instead. I have another box say sirus: then I want to login as a

different user - ssh -X other@sirus If you are the same user ssh -X sirus. Form the window that you executed the command, the X display terminal is now available. If youwant to run say grip, just type grip and the application will now appear in your window. There are several different conditions you have to be carefule whnen running ssh. If you are in your home private world, then just doing that command will work find. It will prompt you for the password. Some more secure conscious people suggest you build a key to the other machine. If you do this setup, it will just let you in. Turning off the firewall is not necessar. You have to have the ssh port open. Of course, you can alwas use openvpn between systems to. Bruce Rogers wrote:

I have been doing the following with SLES 10, and it's worked fine, up until either beta3 or beta4. Beta4 no longer works either.

On a remote Linux box I set DISPLAY=x.x.x.x:0 and launch some X app, targeted to the SLES10 box (with IP addr x.x.x.x) To enable this to work, all I've done is:

1) turn off the firewall 2) in /etc/sysconfig/displaymanager change DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN to "yes" 3) in /etc/sysconfig/displaymanager change DISPLAYMANAGER_REMOTE_ACCESS to "yes" 4) in /etc/X11/xdm/xdm-config change DisplayManager._0.authorize: to false 5) xhost + I must apologize as I don't know much about the security infrastructure of X11. I need this to still work for me. Can anyone tell me why it no longer would be working or what the steps should be to debug this problem.

thanks.

- Bruce Rogers

-- Joseph Loo jloo@acm.org -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com