[Bug 338] New: X11 forwarding no longer works after upgrading from 2.9.9p2 to 3.4p1
bugzilla-daemon at mindrot.org
bugzilla-daemon at mindrot.org
Sat Jul 6 04:20:48 EST 2002
http://bugzilla.mindrot.org/show_bug.cgi?id=338
Summary: X11 forwarding no longer works after upgrading from
2.9.9p2 to 3.4p1
Product: Portable OpenSSH
Version: -current
Platform: Sparc
URL: ftp://gandalf.cc.purdue.edu/pub/ssh/ssh-X11-bug.tgz
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy: jrj at purdue.edu
X11 forwarding no longer works after upgrading from 2.9.9p2 to 3.4p1.
When a client tries to connect it reports:
Xlib: connection to "localhost:20.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: Can't open display: localhost:20.0
Environment is Solaris 2.6 on both sides (ssh and sshd).
This worked just fine before the upgrade (with 2.9.9p2 on both sides).
I have further debugged it to being related to the 3.4p1 client side.
If I connect to either a 2.9.9p2 or 3.4p1 server with a 2.9.9p2 client,
I can start an X11 client. If I connect to either server with a 3.4p1
client, it fails.
I tried both settings for X11UseLocalhost and can see the change to the
DISPLAY environment variable (so I know the X11UseLocalhost change was
taking place), but it made no difference to the problem.
I do not normally have a $HOME/.ssh/rc file. I tried using the example
in the sshd man page, but that also had no effect.
I do not have a $HOME/.ssh/environment or /etc/ssh/sshrc file.
The debugging files, and build output, indicate xauth was found and is
being run.
As far as I recall, I only made two other changes at the time 3.4p1
was installed. One was to put "Protocol 2" in sshd_config to disable
protocol version 1. The other was to comment out some "UseRSH" lines in
my own $HOME/.ssh/config file since that no longer appears to be supported
(which is very unfortunate -- but that's a different matter).
The following file:
ftp://gandalf.cc.purdue.edu/pub/ssh/ssh-X11-bug.tgz
contains copies of my config files, the build environment output, and
log files from my tests.
The test involved two machines. Gandalf is a X11 workstation, i.e. it
has the display. Fortress is another Solaris machine where I wanted to
start an client (xclock) and have it show up on the gandalf display. So
the test, from gandalf, was:
ssh fortress /usr/openwin/bin/xclock
Files named "client.*" are from the ssh side (gandalf). Files named
"server.*" are from the sshd side (fortress). Files named "*ssh-2*"
are using the 2.9.9p2 ssh, while those named "*ssh-3*" are using 3.4p1.
Files named "*sshd-2*" are using the 2.9.9p2 sshd, while those named
"*sshd-3*" are using 3.4p1. All files are with "-v -v -v" and "-d -d -d".
John R. Jackson, Technical Software Specialist, jrj at purdue.edu
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the openssh-unix-dev
mailing list