RE: X and Ssh yet again.

From: Stephanie Schiebert (steph@ssh.com)
Date: 02/07/03

  • Next message: Tim Tominna: "PC based SSH question"
    From: "Stephanie Schiebert" <steph@ssh.com>
    To: "Jorge Aldana" <jorge@salk.edu>, <secureshell@securityfocus.com>
    Date: Fri, 7 Feb 2003 12:19:44 -0500
    
    

    Hi Jorge,

    Try compiling with these options:

    # make distclean
    $ ./configure --without-x11-security
    $ make
    # make install

    Chances are, the X11 Security support added to v 3.2.2 is what is causing your problem.

    Cheers,

    Steph

    *********************************
    Stephanie Schiebert
    Sr. Engineer, Technical Services
    SSH Secure Shell
    GIAC Certified
    Unix Security Administrator
    SSH Communications Security Inc.
    http://www.ssh.com/support/ssh
    *********************************

    -----Original Message-----
    From: Jorge Aldana [mailto:jorge@salk.edu]
    Sent: Thursday, February 06, 2003 10:53 PM
    To: ssh@clinet.fi; secureshell@securityfocus.com
    Subject: X and Ssh yet again.

    Ok, I've tried several posted solutions but still get

    Error: Can't open display:

    when trying to launch an X app remotely.

    This is only true under version v3.2.2 (from ssh.com), under v3.0.1 it works
    fine. I usually compile ssh using all the defaults, which lead me to recompile
    using --with-x (well configure with) and the problem still persists. I even set
    AllowX11Forwarding to yes in sshd2_config and ssh2_config (under /etc/ssh2 and
    restarted the daemon), although none of this was ever needed under v3.0.1. I
    then rummaged through the listings on this list and used several posted
    solutions like:

    ssh -R 6009:localhost:6000 foo.bar.com

    or

    ssh +X foo.bar.com

    and then even tried setting DISPLAY manually and still get the dreaded "Error:
    Can't open display:", not that I wanted to.

    I'm using several different OS's and they behave the same, or I get the same
    behavior with the same version of ssh. Has something changed that has slipped by
    me?

    Using v3.0.1 the DISPLAY variable is automatically set as it should but under
    v3.2.2 there isn't even a DISPLAY variable listed.

    Anyone know of any possible hangups here?

    Jorge