Results 1 to 4 of 4

Thread: SSH Error

  1. #1
    Just burned their ISO
    Join Date
    Nov 2012
    Posts
    7

    Question SSH Error

    When I try to tunnel my traffic from my one system to another I get an ssh error and the connection breaks. But if I simply connect to my ssh server the connection works fine.

    Error:
    Code:
    root@bt:~# ssh -v -g -N -D 31154 xp@192.168.1.5
    OpenSSH_6.1p1, OpenSSL 0.9.8k 25 Mar 2009
    debug1: Reading configuration data /usr/local/etc/ssh_config
    debug1: Connecting to 192.168.1.5 [192.168.1.5] port 22.
    debug1: Connection established.
    debug1: permanently_set_uid: 0/0
    debug1: identity file /root/.ssh/id_rsa type -1
    debug1: identity file /root/.ssh/id_rsa-cert type -1
    debug1: identity file /root/.ssh/id_dsa type -1
    debug1: identity file /root/.ssh/id_dsa-cert type -1
    debug1: identity file /root/.ssh/id_ecdsa type -1
    debug1: identity file /root/.ssh/id_ecdsa-cert type -1
    debug1: Remote protocol version 2.0, remote software version WeOnlyDo 2.1.3
    debug1: no match: WeOnlyDo 2.1.3
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_6.1
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: server->client aes128-cbc hmac-md5 none
    debug1: kex: client->server aes128-cbc hmac-md5 none
    debug1: sending SSH2_MSG_KEXDH_INIT
    debug1: expecting SSH2_MSG_KEXDH_REPLY
    debug1: Server host key: RSA 46:60:5d:61:2e:c2:22:1a:ab:f6:d6:e8:ec:8d:3e:41
    The authenticity of host '192.168.1.5 (192.168.1.5)' can't be established.
    RSA key fingerprint is 46:60:5d:61:2e:c2:22:1a:ab:f6:d6:e8:ec:8d:3e:41.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added '192.168.1.5' (RSA) to the list of known hosts.
    debug1: ssh_rsa_verify: signature correct
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: Roaming not allowed by server
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue: password,publickey
    debug1: Trying private key: /root/.ssh/id_rsa
    debug1: Trying private key: /root/.ssh/id_dsa
    debug1: Trying private key: /root/.ssh/id_ecdsa
    debug1: Next authentication method: password
    xp@192.168.1.5's password: 
    debug1: Authentication succeeded (password).
    Authenticated to 192.168.1.5 ([192.168.1.5]:22).
    debug1: Local connections to *:31154 forwarded to remote address socks:0
    debug1: Local forwarding listening on 0.0.0.0 port 31154.
    debug1: channel 0: new [port listener]
    debug1: Local forwarding listening on :: port 31154.
    debug1: channel 1: new [port listener]
    debug1: Entering interactive session.
    debug1: Connection to port 31154 forwarding to socks port 0 requested.
    debug1: channel 2: new [dynamic-tcpip]
    buffer_get_ret: trying to get more bytes 4 than in buffer 0
    buffer_get_string_ret: cannot extract length
    buffer_get_string: buffer error
    root@bt:~#
    On googling I found people saying that deleting the "known_hosts" file in .ssh directory can fix it (because of corruption due to newline character). But it also didn't work.
    I tried to do the same in BT5, BT5r2, BT5r3 and I m facing the same problem in all of them.
    Anyone else facing the same problem?
    Last edited by g0tmi1k; 11-09-2012 at 02:34 PM. Reason: Added CODE tags

  2. #2
    Very good friend of the forum Gitsnik's Avatar
    Join Date
    Jan 2010
    Location
    The Crystal Wind
    Posts
    851

    Default Re: SSH Error

    My experience says it's the ~/.ssh/authorized_keys file, not known_hosts. Try moving it elsewhere or deleting it entirely.
    Still not underestimating the power...

    There is no such thing as bad information - There is truth in the data, so you sift it all, even the crap stuff.

  3. #3
    Just burned their ISO
    Join Date
    Nov 2012
    Posts
    7

    Default Re: SSH Error

    Thank you. But there is no such file in my .ssh directory.

  4. #4
    Just burned their ISO
    Join Date
    Nov 2012
    Posts
    7

    Default Re: SSH Error

    SOLVED
    The problem was with the SSH server. I was using freesshd. I replaced it with winsshd and it worked perfectly.

    Thank you.

Similar Threads

  1. Replies: 0
    Last Post: 10-25-2012, 01:37 AM
  2. Replies: 3
    Last Post: 06-09-2012, 04:27 PM
  3. Booting Error -USB Drive Install -Looping Error After First Boot
    By Spinez in forum BackTrack 5 Beginners Section
    Replies: 8
    Last Post: 06-08-2012, 04:04 PM
  4. Replies: 0
    Last Post: 01-27-2011, 04:06 AM
  5. Replies: 3
    Last Post: 10-18-2010, 11:00 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •