| View previous topic :: View next topic |
| Author |
Message |
pahud
Tux's lil' helper
Joined: 26 Nov 2002
Posts: 103
|
 Posted: Wed Oct 13, 2004 2:20 am Post subject: ssh connection cannot be established |
 |
|
Hello guys,
I cannot ssh connect one of my gentoo servers and I can't find any way to solve this problem. Someone having the same experience?
| Code: | $ ssh -v -v -v myserver
OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading configuration data /export/home/pahud/.ssh/config
debug1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to dev [xxx.xxx.xxx.xxx] port 22.
debug1: Connection established.
debug1: identity file /export/home/pahud/.ssh/identity type -1
debug3: Not a RSA1 key file /export/home/pahud/.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 /export/home/pahud/.ssh/id_rsa type 1
debug1: identity file /export/home/pahud/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.8.1p1
debug1: match: OpenSSH_3.8.1p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1
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-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: 128/256
debug2: bits set: 498/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /export/home/pahud/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 29
debug3: check_host_in_hostfile: filename /export/home/pahud/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 29
debug1: Host 'dev' is known and matches the RSA host key.
debug1: Found key in /export/home/pahud/.ssh/known_hosts:29
debug2: bits set: 494/1024
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
debug2: key: imported-openssh-key (0x80910a0)
debug2: key: /export/home/pahud/.ssh/identity ((nil))
debug2: key: /export/home/pahud/.ssh/id_rsa (0x808b2c8)
debug2: key: /export/home/pahud/.ssh/id_dsa ((nil))
Connection closed by xxx.xxx.xxx.xxx
|
|
|
| Back to top |
|
 |
allistarM
Tux's lil' helper
Joined: 22 Jul 2004
Posts: 141
|
| Posted: Wed Oct 13, 2004 6:34 am Post subject: |
|
|
Yes, I'm having the exact same issue. I updated my 3 gentoo boxes this morning and now I can't ssh to any of them. The emerge -world I did this morning included rdesktop-1.3.1, glibc-2.3.4.20040808-r1 and openoffice-1.1.3. I suspect that the glibc update is causing the problem.
Note that from my gentoo box at hjome I can ssh to a debian server, and I can also ssh back from the debian server to the same gentoo box. I can't connect from debian to a different gentoo box though, only backck to the original one I ssh to the debia box from. I'm not sure is ssh uses the same tunnel for a reverse connection like this.
I am unfamiliar with downgrading glibc to the previous version I had before this morning, can anyone give me any pointers?
Is there a known fixfor this ssh/glibc issue?
I have prelinked my executables, I'll re-prelink them with "prelink -afmR" and will see if that makes a difference. |
|
| Back to top |
|
|
allistarM
Tux's lil' helper
Joined: 22 Jul 2004
Posts: 141
|
| Posted: Wed Oct 13, 2004 6:42 am Post subject: |
|
|
I found the following post that was posted not too long ago that agrees with my glibc suspicions.
https://forums.gentoo.org/viewtopic.php?t=236119
If I restart sshd on the other two Gentoo boxes then I should be able to connect. I just wish I could ssh in to do it, they are 10 k's away and it's late  . |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
