openssh bugs - Apr 2004 - [Bug 832] X forwarding crashes on some applications

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

           Summary: X forwarding crashes on some applications
           Product: Portable OpenSSH
           Version: 3.8p1
          Platform: ix86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ssh
        AssignedTo: openssh-bugs at mindrot.org
        ReportedBy: ktaylor at daac.gsfc.nasa.gov


Two linux boxes running 3.8p1. I log into one of the machines and run xcdroast
(for example), and the screen comes up, but as soon as something in the window
changes (highlighting a button, or clicking on a button), the window crashes
with an error like this:

Gdk-ERROR **: BadWindow (invalid Window parameter)
  serial 345 error_code 3 request_code 38 minor_code 0
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
  serial 346 error_code 10 request_code 102 minor_code 0

This does not happen when using the old ssh CLIENT to connect. So, it seems the
problem is not server related.

I will try to attach the verbose output of the session.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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





------- Additional Comments From ktaylor at daac.gsfc.nasa.gov  2004-04-06 00:55
-------
Created an attachment (id=595)
 --> (http://bugzilla.mindrot.org/attachment.cgi?id=595&action=view)
verbose output (X related stuff)




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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





------- Additional Comments From mouring at eviladmin.org  2004-04-06 00:58
-------
This is not a bug...

man ssh_config
[..]
     ForwardX11Trusted
             If the this option is set to ``yes'' then remote X11
clients will
             have full access to the original X11 display.  If this option is
             set to ``no'' then remote X11 clients will be considered
untrust-
             ed and prevented from stealing or tampering with data belonging
             to trusted X11 clients.

             The default is ``no''.

             See the X11 SECURITY extension specification for full details on
             the restrictions imposed on untrusted clients.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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





------- Additional Comments From dtucker at zip.com.au  2004-04-06 01:00 -------
This?
http://www.openssh.com/faq.html#3.13
[quote]
3.13 - I upgraded to OpenSSH 3.8 and some X11 programs stopped working.

As documented in the 3.8 release notes, ssh will now use untrusted X11 cookies
by default. The previous behaviour can be restored by setting ForwardX11Trusted
yes in ssh_config.
[/quote]

If this is the cause, we should update the FAQ to include the symptoms you saw.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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





------- Additional Comments From ktaylor at daac.gsfc.nasa.gov  2004-04-06 01:50
-------
Yes. That seems to fix it. Thanks. 

I guess I should have read the man pages over again to catch some updated
options.






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

dtucker at zip.com.au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From dtucker at zip.com.au  2004-04-06 08:34 -------
I've added the errors you gave as examples in the FAQ entry.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.