RE: Problems acrossed platforms.

From: Mark Senior (Mark.Senior_at_gov.ab.ca)
Date: 10/06/05

  • Next message: Bhalaji Narayanan: "Not attached to tty..."
    Date: Thu, 6 Oct 2005 11:59:28 -0600
    To: "Jim C." <jlistnews@gmail.com>
    
    

     Are you running ssh from the Terminal in OS X, or from an xterm inside
    of X11? I haven't tried doing that since 10.2.something, so the details
    may have changed.

    At that time though, I had to start X11, open an xterm (not
    Terminal.app), and ssh -X from there.

    My understanding though is that the ssh client can't handle the X11
    connections at its end, since it's not part of an X11 session itself.

    Regards
    Mark

    -----Original Message-----
    From: Jim C. [mailto:jlistnews@gmail.com]
    Sent: Wednesday, October 05, 2005 10:28 AM
    To: secureshell@securityfocus.com
    Subject: Problems acrossed platforms.

    I can't get X11 forwarding to work between Redhat 9 and Mac OS X.

    The Mac box is my desktop box. The Redhat box is on a KVM switch in the
    server room. SSH versions are:

    On Rehat: OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f

    On Mac OS X: OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0,
    OpenSSL 0x0090707f

    Connection transcript is as follows:

    [jamesc@marvin jamesc]$ ssh -vv faap2@grumpy
    OpenSSH_3.6.1p1+CAN-2004-0175, SSH protocols 1.5/2.0, OpenSSL 0x0090707f
    debug1: Reading configuration data /etc/ssh_config
    debug1: Applying options for *
    debug1: Rhosts Authentication disabled, originating port will not be
    trusted.
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to grumpy [192.168.1.228] port 22.
    debug1: Connection established.
    debug2: key_type_from_name: unknown key type '-----BEGIN'
    debug2: key_type_from_name: unknown key type '-----END'
    debug1: identity file /Users/jamesc/.ssh/id_dsa type 2
    debug1: Remote protocol version 1.99, remote software version
    OpenSSH_3.5p1
    debug1: match: OpenSSH_3.5p1 pat
    OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_3.5*
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1+CAN-2004-0175
    debug1: Miscellaneous failure
    Server not found in Kerberos database

    debug1: Miscellaneous failure
    Server not found in Kerberos database

    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug2: kex_parse_kexinit:
    diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
    debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c
    bc,rijndael-cbc@lysator.liu.se
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c
    bc,rijndael-cbc@lysator.liu.se
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-9
    6,hmac-md5-96
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-9
    6,hmac-md5-96
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit: first_kex_follows 0
    debug2: kex_parse_kexinit: reserved 0
    debug2: kex_parse_kexinit:
    diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
    debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c
    bc,rijndael-cbc@lysator.liu.se
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-c
    bc,rijndael-cbc@lysator.liu.se
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-9
    6,hmac-md5-96
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-9
    6,hmac-md5-96
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit: first_kex_follows 0
    debug2: kex_parse_kexinit: reserved 0
    debug2: mac_init: found hmac-md5
    debug1: kex: server->client aes128-cbc hmac-md5 none
    debug2: mac_init: found hmac-md5
    debug1: kex: client->server aes128-cbc hmac-md5 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug2: dh_gen_key: priv key bits set: 131/256
    debug2: bits set: 1597/3191
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug1: Host 'grumpy' is known and matches the RSA host key.
    debug1: Found key in /Users/jamesc/.ssh/known_hosts:17
    debug2: bits set: 1565/3191
    debug1: ssh_rsa_verify: signature correct
    debug2: kex_derive_keys
    debug2: set_newkeys: mode 1
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug2: set_newkeys: mode 0
    debug1: SSH2_MSG_NEWKEYS received
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug2: service_accept: ssh-userauth
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue:
    publickey,password,keyboard-interactive
    debug1: Next authentication method: publickey
    debug1: Trying private key: /Users/jamesc/.ssh/id_rsa
    debug1: Offering public key: /Users/jamesc/.ssh/id_dsa
    debug2: we sent a publickey packet, wait for reply
    debug1: Server accepts key: pkalg ssh-dss blen 434 lastkey 0x300cb0 hint
    1
    debug2: input_userauth_pk_ok: fp
    c7:96:d0:3b:ed:77:56:a7:df:a9:ab:0a:3a:e1:10:d3
    debug1: read PEM private key done: type DSA
    debug1: Authentication succeeded (publickey).
    debug1: channel 0: new [client-session]
    debug2: channel 0: send open
    debug1: Entering interactive session.
    debug2: callback start
    debug2: ssh_session2_setup: id 0
    debug1: channel 0: request pty-req
    debug2: x11_get_proto: /usr/X11R6/bin/xauth list :0.0 2>/dev/null
    debug1: Requesting X11 forwarding with authentication spoofing.
    debug1: channel 0: request x11-req
    debug1: channel 0: request shell
    debug2: callback done
    debug1: channel 0: open confirm rwindow 0 rmax 32768
    debug2: channel 0: rcvd adjust 131072
    faap2@CCB ./faap2 $

    If I ssh to my Mandrake box at home, there is no trouble with X11
    forwarding.

    Jim C.

    This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


  • Next message: Bhalaji Narayanan: "Not attached to tty..."

    Relevant Pages

    • Solaris->Fedora6 unidirectional problem
      ... I have a strange unsolved unidirectional problem using ssh from Solaris to Fedora6: ... I have a couple FC6 behind the Solaris boxes ... debug2: fd 4 setting O_NONBLOCK ... debug1: fd 4 clearing O_NONBLOCK ...
      (SSH)
    • Re: X11 tuneling: a hard to fix problem
      ... I found a similar problem where I had SSH ... The entire point of using ssh for X11 forwarding is that the ssh ... debug1: Connecting to remoteserver port 22. ... debug2: fd 3 setting O_NONBLOCK ...
      (SSH)
    • Problem with password-less logins and OS X Panther
      ... I frequently SSH from my Linux ... debug1: Rhosts Authentication disabled, originating port will not be trusted. ... debug2: ssh_connect: needpriv 0 ...
      (SSH)
    • Re: X11 tuneling: a hard to fix problem
      ... debug1: Connecting to remoteserver port 22. ... debug2: fd 3 setting O_NONBLOCK ... Requesting X11 forwarding with authentication spoofing. ... debug2: channel 0: request pty-req confirm 0 ...
      (SSH)
    • X11 tuneling: a hard to fix problem
      ... debug1: Connecting to remoteserver port 22. ... debug2: fd 3 setting O_NONBLOCK ... Requesting X11 forwarding with authentication spoofing. ... debug2: channel 0: request pty-req confirm 0 ...
      (SSH)