After ssh'ing to self machine, unable to display xclock???

Passions · 02-23-2008, 07:20 PM

When I'm on a machine let's say called host1, I can enter:

Code:

xclock -display host1:0.0

and xclock will display on the local machine.

After I ssh to the same machine and enter the password (we have software that ssh's to itself)

Code:

ssh host1
<password>
 xclock -display host1:0.0

I get an error:

Code:

Xlib: connection to "host1:0.0" refused by server. 
Xlib: No protocol specified
Error: Can't open display: host1:0.0

I tried deleting the user's .ICEAuthority and .Xauthority files, logged out, logged in. It recreated them, but still same error.

I know "xhost +" would work and I tried it, but I'd like to avoid it since the security holes.

I also created a new user and tried sshing to myself and it works! I'm just wondering how I can fix this particular user's problem. It has to do something with the user's NFS mounted home directory, right? Some files must be corrupted.

druuna · 02-24-2008, 04:34 AM

Hi,

Have you tried using ssh's -X option (ssh -X host1)? It (X11 forwarding) is also present in gui clients (putty for example).

The -X option (see man page) is a way of enabling X11 forwarding without the need of xhost, export DISPLAY, etc.

Hope this helps.

Passions · 02-24-2008, 11:02 AM

Yes, I tried ssh with -X option. It doesn't work either. Still the Xlib errors.

This is really bizarre how I can do it with another user. I'm thinking it has to do something with the home directory files. argggghghghgh.

Passions · 02-25-2008, 03:25 PM

I solved my problem. Apparently if the user's home directory is set to 775, it causes this issue. If you chmod to 700, it works without the errors.

druuna · 02-25-2008, 04:12 PM

Hi,

The .ssh directory needs 700, otherwise ssh won't accept the files that are there. If your machine is setup correctly you don't have to change the homedir (and all subdirs) to 700, only the .ssh dir.