openssh unix dev - Mar 2002 - 3.1p1 breaks X11 forwarding

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.

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
message.

Received disconnect from 216.17.153.58: 2: Received ieof for nonexistent channel
8.

Sorry I don't have solutions.  I just thought I would report the
problems.  Thanks for carying the torch with this wonderful useful
program.

Bob

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?

     X11UseLocalhost
             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''.

also:
http://bugzilla.mindrot.org/show_bug.cgi?id=150

: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
:message.
:
:Received disconnect from 216.17.153.58: 2: Received ieof for nonexistent
channel 8.

can you submit that (plus exact how-to-dup details) to
http://bugzilla.mindrot.org/