[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[suse-security] ssh and X11 help



I am reposting this question since I wasn't able to find a solution:

PRODUCT: SuSE Linux (I386) 9.0
I have a problem opening an Xterm window on my Suse linux machine (SL) after I ssh (with X11 forwarding) to a remote machine (RM).


The display is set correctly, I see the xterm process running on the remote machine but the xterm does not pop up on my Suse linux machine (SL). In fact I lose keyboard input capabilities in the window where I typed 'xterm' and I only get it back one the connection times out.

The IMPORTANT part is that I can accomplish the same thing from a Windows machine from the same network as my SL machine via putty (win ssh client) and Exceed. That indicates that the issue is with my local SUSE setup. The last line of the verbosed ouput is identical in both cases:

"confirm x11"

except on the Suse machine my xterm window doesn't pop up, on the windows machine it does. This leads me to believe that tI have a Suse ssh (maybe X) related problem. I tried the newest ssh and older versions as well. I also built putty on Suse Linux and I got the same behavior

One other important issue: to reach to my remote machine I ssh twice:

1.  Suse Linux to remote account management machine (RAM).
2.  RAM to RM ( where I finally want the xterm to run)

In all cases the displays are set correctly. I also verified the xauth -list and my display is in the output and has a magic cookie.

Please let me know if you have any ideas about how to solve this problem. Any suggestions will be highly appreciated.

Additional info below:

** my SUSE (SL) machine
suse{cduma}41: ssh -V
OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.7b 10 Apr 2003

** the RAM machine (after the 1st ssh from SL to RAM)
gatekeeper% ssh -V
OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f

gatekeeper% echo $DISPLAY
gatekeeper:14.0

** the RM machine (where I want to do the work and start the xterm)
shaman{cduma}1: echo $DISPLAY
shaman:10.0

** the RM machine ouput after I start the Xterm
shaman{cduma}2: debug2: client_check_window_change: changed
debug2: channel 0: request window-change
debug2: client_check_window_change: changed
debug1: channel request 0: window-change
shaman{cduma}4: xterm
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from <ipaddress_here> 42287
debug2: fd 7 setting O_NONBLOCK
debug2: fd 7 is O_NONBLOCK
debug1: channel 1: new [x11]
debug1: confirm x11
debug1: client_input_channel_open: ctype x11 rchan 1 win 30000 max 1024
debug1: client_request_x11: request from <ipaddress_here>  45345
debug1: fd 7 setting TCP_NODELAY
debug1: fd 7 setting O_NONBLOCK
debug2: fd 7 is O_NONBLOCK
debug1: channel 1: new [x11]
debug1: confirm x11

** above is where the xterm window pops uo on my Windows machine, it doesn't on my SUSE machine

** below is the logging after connection TIMEOUT

debug1: channel 0: free: client-session, nchannels 2
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i0/0 o0/0 fd 4/5)
#1 x11 (t4 r3 i0/0 o0/0 fd 7/7)

debug3: channel 0: close_fds r 4 w 5 e 6
debug1: channel 1: free: x11, nchannels 1
debug3: channel 1: status: The following connections are open:
#1 x11 (t4 r3 i0/0 o0/0 fd 7/7)

debug3: channel 1: close_fds r 7 w 7 e -1
Read from remote host gatekeeper: Connection timed out
Connection to gatekeeper closed.
debug1: Transferred: stdin 0, stdout 0, stderr 118 bytes in 1327.8 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.1
debug1: Exit status -1

Thank you very much.

Calin



--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@suse.com
Security-related bug reports go to security@suse.de, not here