From: Henrik Carlqvist on
Mike Jones <Not(a)Arizona.Bay> wrote:
> Don't worry about silly questions, the problem is silly. :)

Are you able to find any clue to the cause if you do something like:

ssh -vvv -X remotemachine

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Henrik Carlqvist on
Mike Jones <Not(a)Arizona.Bay> wrote:

> Responding to Henrik Carlqvist:
>> Are you able to find any clue to the cause if you do something like:
>>
>> ssh -vvv -X remotemachine

> Only that the connection Can't open display "localhost:10.0"

Even if you are unable to read anything out from the debug messages
someone else might be able to tell something. Please do the following:

ssh -vvv -X remotemachine ls /dev/null >& /tmp/log.txt

Then post your contents of /tmp/log.txt

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Henrik Carlqvist on
Mike Jones <Not(a)Arizona.Bay> wrote:
> debug1: Authentication succeeded (publickey).
> debug2: fd 5 setting O_NONBLOCK
> debug3: fd 6 is O_NONBLOCK
> debug1: channel 0: new [client-session]
> debug3: ssh_session2_open: channel_new: 0
> debug2: channel 0: send open
> debug1: Requesting no-more-sessions(a)openssh.com
> debug1: Entering interactive session.
> debug2: callback start
> debug2: x11_get_proto: /usr/bin/xauth list :0.0 2>/dev/null
> debug1: Requesting X11 forwarding with authentication spoofing.
> debug2: channel 0: request x11-req confirm 0
> debug2: client_session2_setup: id 0
> debug1: Sending command: ls /dev/null

I can't say for sure why it goes wrong, but when I compare with my own log
I have some other xauth lines:

debug1: Authentication succeeded (publickey).
debug3: clear hostkey 1
debug3: clear hostkey 2
debug2: fd 5 setting O_NONBLOCK
debug3: fd 6 is O_NONBLOCK
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: x11_get_proto: /usr/X11R6/bin/xauth -f /tmp/ssh-cmtAy20610/xauthfile generate :0.0 MIT-MAGIC-COOKIE-1 untrusted timeout 1200 2>/dev/null
debug2: x11_get_proto: /usr/X11R6/bin/xauth -f /tmp/ssh-cmtAy20610/xauthfile list :0.0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 0
debug2: client_session2_setup: id 0
debug1: Sending command: ls /dev/null

However, the difference might be explained by the fact that I am doing the
test on a rather old Slackware 9.1 installation.

Are you able to start some X program on your local console machine from
the terminal where you later call ssh? If you for some reason would be
unable to start local X applications you would also not be able to tunnel
X with ssh as your ssh client then behaves like an X application.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Lew Pitcher on
On February 9, 2010 15:09, in alt.os.linux.slackware,
Henrik.Carlqvist(a)deadspam.com wrote:

> Mike Jones <Not(a)Arizona.Bay> wrote:
>> debug1: Authentication succeeded (publickey).
>> debug2: fd 5 setting O_NONBLOCK
>> debug3: fd 6 is O_NONBLOCK
>> debug1: channel 0: new [client-session]
>> debug3: ssh_session2_open: channel_new: 0
>> debug2: channel 0: send open
>> debug1: Requesting no-more-sessions(a)openssh.com
>> debug1: Entering interactive session.
>> debug2: callback start
>> debug2: x11_get_proto: /usr/bin/xauth list :0.0 2>/dev/null
>> debug1: Requesting X11 forwarding with authentication spoofing.
>> debug2: channel 0: request x11-req confirm 0
>> debug2: client_session2_setup: id 0
>> debug1: Sending command: ls /dev/null
>
> I can't say for sure why it goes wrong, but when I compare with my own log
> I have some other xauth lines:
>
> debug1: Authentication succeeded (publickey).
> debug3: clear hostkey 1
> debug3: clear hostkey 2
> debug2: fd 5 setting O_NONBLOCK
> debug3: fd 6 is O_NONBLOCK
> debug1: channel 0: new [client-session]
> debug3: ssh_session2_open: channel_new: 0
> debug2: channel 0: send open
> debug1: Entering interactive session.
> debug2: callback start
> debug2: x11_get_proto: /usr/X11R6/bin/xauth -f
> /tmp/ssh-cmtAy20610/xauthfile generate :0.0 MIT-MAGIC-COOKIE-1 untrusted
> timeout 1200 2>/dev/null debug2: x11_get_proto: /usr/X11R6/bin/xauth -f
> /tmp/ssh-cmtAy20610/xauthfile list :0.0 2>/dev/null debug1: Requesting X11
> forwarding with authentication spoofing. debug2: channel 0: request
> x11-req confirm 0 debug2: client_session2_setup: id 0 debug1: Sending
> command: ls /dev/null

FWIW, here's another successful log to compare against

X client (ssh server) is fully patched and current Slackware 13.0
X server (ssh client) is fully patched and current Slackware 12.0
Command was: ssh -vvv -X merlin xclock >& /tmp/log.txt

debug1: Authentication succeeded (publickey).
debug2: fd 5 setting O_NONBLOCK
debug3: fd 6 is O_NONBLOCK
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Requesting no-more-sessions(a)openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: x11_get_proto: /usr/bin/xauth -f /tmp/ssh-ZZsYWH7725/xauthfile
generate :0.0 MIT-MAGIC-COOKIE-1 untrusted timeout 1200 2>/dev/null
debug2: x11_get_proto: /usr/bin/xauth -f /tmp/ssh-ZZsYWH7725/xauthfile
list :0.0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 0
debug2: client_session2_setup: id 0
debug1: Sending command: xclock
debug2: channel 0: request exec confirm 1
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_confirm: type 99 id 0
debug2: exec request accepted on channel 0
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 38013
debug2: fd 7 setting O_NONBLOCK
debug3: fd 7 is O_NONBLOCK
debug1: channel 1: new [x11]
debug1: confirm x11



--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------


From: Henrik Carlqvist on
Lew Pitcher <lpitcher(a)teksavvy.com> wrote:
> FWIW, here's another successful log to compare against

> debug2: x11_get_proto: /usr/bin/xauth -f /tmp/ssh-ZZsYWH7725/xauthfile
> generate :0.0 MIT-MAGIC-COOKIE-1 untrusted timeout 1200 2>/dev/null
> debug2: x11_get_proto: /usr/bin/xauth -f /tmp/ssh-ZZsYWH7725/xauthfile
> list :0.0 2>/dev/null

Yep, you get the same kind of xauth lines that I do. On the other hand Jim
Diamond gets the same xauth line as Mike Jones and it works for Jim.

I really can't tell what is going wrong, I have been trying to provocate
my machines to get the error, but the closest I get is this attempt:

> xclock
(local xclock shows up on display)
> unsetenv DISPLAY
> xclock
Error: Can't open display:
> ssh -X mugin xclock
Error: Can't open display:

Even though I get an error about the display from my ssh session I am not
able to get the error about display localhost:10.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost