1848700 Members
6961 Online
104036 Solutions
New Discussion

Memory fault from ssh

 
SOLVED
Go to solution
Alessio_6
Occasional Advisor

Memory fault from ssh

Hello,

we have problem while doing ssh from version 3.5 to a server 3.7.1; while doing ssh to the same version, it works correctly.
ssh crashes generating a core.
Below the output from ssh and sshd.


afis_svr:/#ssh -vvv n4000m
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090609f
751: debug1: Reading configuration data /opt/ssh/etc/ssh_config
751: debug3: Seeding PRNG from /opt/ssh/libexec/ssh-rand-helper
751: debug1: Rhosts Authentication disabled, originating port will not be trusted.
751: debug1: ssh_connect: needpriv 0
751: debug1: Connecting to n4000m [172.16.50.36] port 22.
751: debug1: Connection established.
751: debug3: Not a RSA1 key file /.ssh/id_rsa.
751: debug2: key_type_from_name: unknown key type '-----BEGIN'
751: debug3: key_read: no key found
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug2: key_type_from_name: unknown key type '-----END'
751: debug3: key_read: no key found
751: debug1: identity file /.ssh/id_rsa type 1
751: debug3: Not a RSA1 key file /.ssh/id_dsa.
751: debug2: key_type_from_name: unknown key type '-----BEGIN'
751: debug3: key_read: no key found
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug3: key_read: no space
751: debug2: key_type_from_name: unknown key type '-----END'
751: debug3: key_read: no key found
751: debug1: identity file /.ssh/id_dsa type 2
751: debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p2-pwexp26
751: debug1: match: OpenSSH_3.7.1p2-pwexp26 pat OpenSSH*
751: debug1: Enabling compatibility mode for protocol 2.0
751: debug1: Local version string SSH-2.0-OpenSSH_3.5p1
Memory fault(coredump)



n4000m:/#sshd -ddd
debug3: Seeding PRNG from /opt/ssh/libexec/ssh-rand-helper
debug2: read_server_config: filename /opt/ssh/etc/sshd_config
debug1: sshd version OpenSSH_3.7.1p2-pwexp26 [ HP-UX_Secure_Shell-A.03.71.000 ]
debug1: private host key: #0 type 0 RSA1
debug3: Not a RSA1 key file /opt/ssh/etc/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: Not a RSA1 key file /opt/ssh/etc/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Server will not fork when running in debugging mode.
Connection from 172.16.50.20 port 61244
debug1: Client protocol version 2.0; client 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.7.1p2-pwexp26
debug2: Network child is on pid 29629
debug3: preauth child monitor started
debug3: mm_request_receive entering
debug3: privsep user:group 103:102
debug1: permanently_set_uid: 103/102
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
Connection closed by 172.16.50.20
debug1: Calling cleanup 0x4001505a(0x0)


thanks,
Alessio
3 REPLIES 3
Charles Harris
Super Advisor

Re: Memory fault from ssh

Hi,

I've never seen ssh crash out in this way, but the top of the ssh debug output seems to be moaning about the lack of a valid host key for the connection. Have you generated new id_dsa keys after the upgrade on the client machines?

Which way round causes the failure, new version connecting to old version or vise versa?

Cheers,

-=ChaZ=-
RAC_1
Honored Contributor

Re: Memory fault from ssh

What does the following command says.

file core

Execute following.
adb /file_core
Once on adb prompt, do $c or $C

Post the results.

Anil
There is no substitute to HARDWORK
Alex Glennie
Honored Contributor
Solution

Re: Memory fault from ssh

it's a known issue : only affects HP's ssh 3.5 on 11.11 I beleive : down to differences in the version string .... you'll need to upgrade to 3.6 or greater : fyi 3.8.1 just got released this week

file core should yield memory fault / sigsegv ....