Re: Host key verification failed

From: Gaspar de Elías (gaspar.delias_at_gmail.com)
Date: 11/19/04

  • Next message: Robert Moss: "RE: Host key verification failed"
    Date: Thu, 18 Nov 2004 20:57:56 -0300
    To: "wilis@dcc.ufmg.br" <wilis@dcc.ufmg.br>
    
    

    Have you tried to update your ssh client?. I dunno so much of this,
    but it seems that you're using and older version than server's ssh
    version. Maybe you're using ssh, and the server is ssh2.

    I wouldn't be surprised if i'm talking bullshit, and please let me
    know if i'm wrong. I just wanted to post what i was thinking.

    thanks

    On Thu, 18 Nov 2004 10:46:39 -0200 (BRDT), wilis@dcc.ufmg.br
    <wilis@dcc.ufmg.br> wrote:
    > Hi,
    >
    > I'm using ssh client in a Slackware distribution Linux and trying to
    > connect to ssh server on mica.dcc.ufmg.br. But I can't connect to it and
    > can't connect to any other server.
    >
    > root@status:/var/tmp# ssh -version
    > OpenSSH_3.9p1, OpenSSL 0.9.7d 17 Mar 2004
    >
    > I need help. Thanks !
    >
    > This is the debug messages:
    >
    > root@status:/var/tmp# ssh mica.dcc.ufmg.br -l root -vvv
    > OpenSSH_3.9p1, OpenSSL 0.9.7d 17 Mar 2004
    > debug1: Reading configuration data /usr/local/etc/ssh_config
    > debug2: ssh_connect: needpriv 0
    > debug1: Connecting to mica.dcc.ufmg.br [150.164.0.134] port 22.
    > debug1: Connection established.
    > debug1: permanently_set_uid: 0/0
    > debug1: identity file /root/.ssh/identity type -1
    > debug3: Not a RSA1 key file /root/.ssh/id_rsa.
    > debug2: key_type_from_name: unknown key type '-----BEGIN'
    > debug3: key_read: missing keytype
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug2: key_type_from_name: unknown key type '-----END'
    > debug3: key_read: missing keytype
    > debug1: identity file /root/.ssh/id_rsa type 1
    > debug1: identity file /root/.ssh/id_dsa type -1
    > debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p2
    > debug1: match: OpenSSH_3.7.1p2 pat OpenSSH*
    > debug1: Enabling compatibility mode for protocol 2.0
    > debug1: Local version string SSH-2.0-OpenSSH_3.9p1
    > debug2: fd 3 setting O_NONBLOCK
    > debug1: SSH2_MSG_KEXINIT sent
    > debug1: SSH2_MSG_KEXINIT received
    > debug2: kex_parse_kexinit:
    > diffie-hellman-group-exchange-sha1,diffie-hellman-group14-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-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    > debug2: kex_parse_kexinit:
    > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,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-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    > debug2: kex_parse_kexinit:
    > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,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(1024<1024<8192) sent
    > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    > debug2: dh_gen_key: priv key bits set: 136/256
    > debug2: bits set: 525/1024
    > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    > debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
    > debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts
    > debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
    > debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts
    > debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
    > debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts
    > debug2: no key of type 0 for host mica.dcc.ufmg.br
    > debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts2
    > debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts2
    > debug3: check_host_in_hostfile: filename /root/.ssh/known_hosts
    > debug3: check_host_in_hostfile: filename /usr/local/etc/ssh_known_hosts
    > debug2: no key of type 2 for host mica.dcc.ufmg.br
    > Host key verification failed.
    >
    >

    -- 
    Gaspar de Elías
    

  • Next message: Robert Moss: "RE: Host key verification failed"

    Relevant Pages

    • Re: "reverse" SOCKS with Putty
      ... I wish to make a tunnel in order to "forward" the LAN to my home ... there are no SSH servers on the network used to play at school. ... by the server to unilaterally set up forwarded connections, ... tunnels for your application in your SSH client. ...
      (comp.security.ssh)
    • Re: Password works Public Key doesnt
      ... > TA> From a WinXP SSH client to a Win2K server I can connect using the ... When I try Public Key, I get this error: Server ... > * SSH client software and version? ...
      (comp.security.ssh)
    • Re: trouble tunneling
      ... JM> VNC server and an SSH server (SSH secure shell server evaluation ... JM> version) running on computer A. I use putty as my ssh client on B ... the SSH server would not be listening on 5900; your VNC server should ...
      (comp.security.ssh)
    • TIPS FOR THE NEWCOMER
      ... Correct me if I am wrong, it appears that ssh and gnupg has similar ... Do I have to send my public key to ... the other machine (ssh client) and likewise do the same thing get a copy ... Is the passphrase function here same as in gnupg that if you have ...
      (SSH)
    • Re: Using public key pair to authenticate
      ... I deliver support for the F-Secure SSH products and have this question ... The best thing to do would be to convert the public key into ... Copy the converted public key over to the SSH Server and place it ... into a tar file and untar them onto the SSH Client ...
      (SSH)