3.1p1 breaks X11 forwarding

Kevin Steves kevin at atomicgears.com
Tue Mar 12 17:11:10 EST 2002

On Mon, 11 Mar 2002, Bob Proulx wrote:
:I just recently updated to 3.1p1 and it seems that some X11 forwarding
:connections are broken while others work.  For instance xterm always
:works fine.  But Synchronize (group calendar program) always crashes
:with the following error.  This happens even if I disable access
:control using 'xhost +'.
:  X11 connection rejected because of wrong authentication.

what OS?

             Specifies whether sshd should bind the X11 forwarding server to
             the loopback address or to the wildcard address.  By default,
             sshd binds the forwarding server to the loopback address and sets
             the hostname part of the DISPLAY environment variable to
             ``localhost''. This prevents remote hosts from connecting to the
             fake display.  However, some older X11 clients may not function
             with this configuration.  X11UseLocalhost may be set to ``no'' to
             specify that the forwarding server should be bound to the wild-
             card address.  The argument must be ``yes'' or ``no''. The de-
             fault is ``yes''.


:Secondly, in going back to 3.0.2p1 to try to work around this problem
:I was able to crash ssh with the following error.  I window killed a
:forwarded xterm which was running a separate X11 program also
:forwarded.  The child tunneled X11 program appeared to hang and I
:killed the application.  This crashed the underlying ssh with this
:Received disconnect from 2: Received ieof for nonexistent channel 8.

can you submit that (plus exact how-to-dup details) to

More information about the openssh-unix-dev mailing list