On Nov 11, 2007 8:28 PM, Ben Byer <email@hidden> wrote:
Okay, try these SSH troubleshooting steps. This list shows the
expected behavior of the system.
[4] local $ ssh -Y remote
Warning: No xauth data; using fake authentication data for X11
forwarding.
[5] remote $ echo $DISPLAY
localhost:10.0
[6]remote $ grep X11 /etc/ssh/sshd_config ~/.ssh/*
X11Forwarding yes
X11DisplayOffset 10
Notes:
The warning message in step 4 is harmless.
If step 5 does not output anything, then step 6 will say
"X11Forwarding no". In this case, you must fix the configuration on
the remote side.
If step 6 outputs anything other than "localhost:xx.0", then your
remote configuration is overriding the DISPLAY variable set by sshd
on
the remote side.
--
Ben Byer
CoreOS / BSD Technology Group, XDarwin maintainer
I get the following upon grep'ing for DISPLAY on the remote host
(running Leo) in [3]:
/sw/etc/alternatives/xdvi.1:.SB DISPLAY.
/sw/etc/alternatives/xdvi.1:.SB DISPLAY
/sw/etc/profile.d/xfontpath.csh:if ( -x "/sw/bin/xfontpath" && $?
DISPLAY ) then
/sw/etc/profile.d/xfontpath.csh: if ( "x$DISPLAY" == x:0.0 ||
"x$DISPLAY" == x:0 ) then
/sw/etc/profile.d/xfontpath.sh: case $DISPLAY in
/etc/sudoers:Defaults env_keep += "DISPLAY XAUTHORIZATION
XAUTHORITY"
I think that last line in the sudoers file is something new; I might
have inadvertently done that at some point in trying to troubleshoot
this?
Locally, [1] runs just fine with the expected output, but after doing
[4], which is what I did in Tiger successfully, [5] now returns an
empty line.
I should mention that [6] was properly set for all of this, though I
recently changed the /etc/ssh_config to read:
ForwardX11Trusted yes
which was not present as an option in the default ssh_config file but
looks to be an option in the man page. (Could this account for my
sudoers file?) Easy enough to change back.
