Re: x11 forwarding problems

From: Robert Hajime Lanning (robert.lanning_at_gmail.com)
Date: 05/17/05

  • Next message: List Account: "RE: Security Practices" 
    Date: Tue, 17 May 2005 10:57:30 -0700
To: secureshell@securityfocus.com

    Has anyone looked to see if j2ssh client talks to the local X server via TCP?

    Most X servers (outside of standalone X terminals) don't listen for TCP
    connections anymore, by default. Instead they either use shared memory
    or Unix domain sockets.

    OpenSSH will connect to the local X server by what ever works, and the
    OpenSSH server emulates a TCP based X server.

    I have some applications that do not run via OpenSSH X forwarding. The
    X server emulation is not complete and I get bad X calls reported. They work
    fine localy. PerlTK seems to be this way. (Invalid Atoms reported.)

    On 5/13/05, Andre Charbonneau <andre.charbonneau@nrc-cnrc.gc.ca> wrote:
    > Hi,
    > If I connect to a openssh server (SSH-1.99-OpenSSH_3.8p1, running on
    > SuSE Linux 9.1 (i586)) using a openssh client (OpenSSH_3.9p1, OpenSSL
    > 0.9.7d 17 Mar 2004, running on SuSE Linux 9.2 (i586)), then X11
    > forwarding works fine.
    >
    > But, if I use j2ssh as a ssh client to connect to the same sshd, then I
    > get the following error in the sshd debug output:
    >
    > debug1: channel 3: new [X11 connection from 127.0.0.1 port 36470]
    > channel 3: open failed: connect failed: Connection refused
    >
    > I've been trying to find what might be the problem for a few days now
    > but with no success.
    > I understand that this is not the place to ask questions about j2ssh.
    > But what I would like to know is the following: In general, is there a
    > well known condition, either at the client or server side, which would
    > cause such a 'connection refused'?
    >
    > Thanks,
    > Andre
    >
    > --
    > Andre Charbonneau
    >
    > 100 Sussex Drive, Rm 2025
    > Research Computing Support, IMSB
    > National Research Council Canada
    > Ottawa, ON, Canada K1A 0R6
    > 613-993-3129 Fax: 613-993-3127
    >
    > 

    -- 
END OF LINE
       -MCP
  • Next message: List Account: "RE: Security Practices"

    Relevant Pages

    • Re: Log Out Issues
      ... your perormance may be worse than TCP. ... would be if your protocol anticipates packet loss and does not ... >>> Lets say the client sends a log out request to the server reliably. ...
      (microsoft.public.win32.programmer.networks)
    • Re: Internal TCP/IP send buffer?
      ... and that has to be decided at your proxy server. ... UDP or a separate TCP connection to the target and periodically ... connections) constitutes a completely different source of latency. ...
      (microsoft.public.win32.programmer.networks)
    • Re: Netzwerkproblem GBit -> 100MBit
      ... GBit-Kette - flow control zwingend notwendig sei. ... zwischen Client und Server. ... Das kann TCP an der Stelle nicht mehr leisten. ...
      (de.comp.sys.novell)
    • Re: RWW Unavailable
      ... SharePoint 444 TCP ... RWW 4125 TCP ... what did you use for your Web Server Certificate? ... This would really look like a router fault if I didn't have the same ...
      (microsoft.public.windows.server.sbs)
    • suspect bug in vge(4)
      ... The high-level view of the problem is that the client seems to stall ... HTTPS server. ... not only printed for TLS/SSL issues but simply also for broken TCP ... To me it sounds like a broken implementation of hardware generated ...
      (freebsd-current)