<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Memory fault from ssh in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337017#M190012</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;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?&lt;BR /&gt;&lt;BR /&gt;Which way round causes the failure, new version connecting to old version or vise versa?&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;-=ChaZ=-</description>
    <pubDate>Wed, 21 Jul 2004 06:43:19 GMT</pubDate>
    <dc:creator>Charles Harris</dc:creator>
    <dc:date>2004-07-21T06:43:19Z</dc:date>
    <item>
      <title>Memory fault from ssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337016#M190011</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;ssh crashes generating a core.&lt;BR /&gt;Below the output from ssh and sshd.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;afis_svr:/#ssh -vvv n4000m&lt;BR /&gt;OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090609f&lt;BR /&gt;751: debug1: Reading configuration data /opt/ssh/etc/ssh_config&lt;BR /&gt;751: debug3: Seeding PRNG from /opt/ssh/libexec/ssh-rand-helper&lt;BR /&gt;751: debug1: Rhosts Authentication disabled, originating port will not be trusted.&lt;BR /&gt;751: debug1: ssh_connect: needpriv 0&lt;BR /&gt;751: debug1: Connecting to n4000m [172.16.50.36] port 22.&lt;BR /&gt;751: debug1: Connection established.&lt;BR /&gt;751: debug3: Not a RSA1 key file /.ssh/id_rsa.&lt;BR /&gt;751: debug2: key_type_from_name: unknown key type '-----BEGIN'&lt;BR /&gt;751: debug3: key_read: no key found&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug2: key_type_from_name: unknown key type '-----END'&lt;BR /&gt;751: debug3: key_read: no key found&lt;BR /&gt;751: debug1: identity file /.ssh/id_rsa type 1&lt;BR /&gt;751: debug3: Not a RSA1 key file /.ssh/id_dsa.&lt;BR /&gt;751: debug2: key_type_from_name: unknown key type '-----BEGIN'&lt;BR /&gt;751: debug3: key_read: no key found&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug3: key_read: no space&lt;BR /&gt;751: debug2: key_type_from_name: unknown key type '-----END'&lt;BR /&gt;751: debug3: key_read: no key found&lt;BR /&gt;751: debug1: identity file /.ssh/id_dsa type 2&lt;BR /&gt;751: debug1: Remote protocol version 2.0, remote software version OpenSSH_3.7.1p2-pwexp26&lt;BR /&gt;751: debug1: match: OpenSSH_3.7.1p2-pwexp26 pat OpenSSH*&lt;BR /&gt;751: debug1: Enabling compatibility mode for protocol 2.0&lt;BR /&gt;751: debug1: Local version string SSH-2.0-OpenSSH_3.5p1&lt;BR /&gt;Memory fault(coredump)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;n4000m:/#sshd -ddd&lt;BR /&gt;debug3: Seeding PRNG from /opt/ssh/libexec/ssh-rand-helper&lt;BR /&gt;debug2: read_server_config: filename /opt/ssh/etc/sshd_config&lt;BR /&gt;debug1: sshd version OpenSSH_3.7.1p2-pwexp26 [ HP-UX_Secure_Shell-A.03.71.000 ]&lt;BR /&gt;debug1: private host key: #0 type 0 RSA1&lt;BR /&gt;debug3: Not a RSA1 key file /opt/ssh/etc/ssh_host_rsa_key.&lt;BR /&gt;debug1: read PEM private key done: type RSA&lt;BR /&gt;debug1: private host key: #1 type 1 RSA&lt;BR /&gt;debug3: Not a RSA1 key file /opt/ssh/etc/ssh_host_dsa_key.&lt;BR /&gt;debug1: read PEM private key done: type DSA&lt;BR /&gt;debug1: private host key: #2 type 2 DSA&lt;BR /&gt;debug1: Bind to port 22 on 0.0.0.0.&lt;BR /&gt;Server listening on 0.0.0.0 port 22.&lt;BR /&gt;debug1: Server will not fork when running in debugging mode.&lt;BR /&gt;Connection from 172.16.50.20 port 61244&lt;BR /&gt;debug1: Client protocol version 2.0; client software version OpenSSH_3.5p1&lt;BR /&gt;debug1: match: OpenSSH_3.5p1 pat OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_3.5*&lt;BR /&gt;debug1: Enabling compatibility mode for protocol 2.0&lt;BR /&gt;debug1: Local version string SSH-2.0-OpenSSH_3.7.1p2-pwexp26&lt;BR /&gt;debug2: Network child is on pid 29629&lt;BR /&gt;debug3: preauth child monitor started&lt;BR /&gt;debug3: mm_request_receive entering&lt;BR /&gt;debug3: privsep user:group 103:102&lt;BR /&gt;debug1: permanently_set_uid: 103/102&lt;BR /&gt;debug1: list_hostkey_types: ssh-rsa,ssh-dss&lt;BR /&gt;debug1: SSH2_MSG_KEXINIT sent&lt;BR /&gt;Connection closed by 172.16.50.20&lt;BR /&gt;debug1: Calling cleanup 0x4001505a(0x0)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;Alessio</description>
      <pubDate>Wed, 21 Jul 2004 02:47:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337016#M190011</guid>
      <dc:creator>Alessio_6</dc:creator>
      <dc:date>2004-07-21T02:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: Memory fault from ssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337017#M190012</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;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?&lt;BR /&gt;&lt;BR /&gt;Which way round causes the failure, new version connecting to old version or vise versa?&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;-=ChaZ=-</description>
      <pubDate>Wed, 21 Jul 2004 06:43:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337017#M190012</guid>
      <dc:creator>Charles Harris</dc:creator>
      <dc:date>2004-07-21T06:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: Memory fault from ssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337018#M190013</link>
      <description>What does the following command says.&lt;BR /&gt;&lt;BR /&gt;file core&lt;BR /&gt;&lt;BR /&gt;Execute following.&lt;BR /&gt;adb /file_core&lt;BR /&gt;Once on adb prompt, do $c or $C&lt;BR /&gt;&lt;BR /&gt;Post the results.&lt;BR /&gt;&lt;BR /&gt;Anil</description>
      <pubDate>Wed, 21 Jul 2004 07:19:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337018#M190013</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2004-07-21T07:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: Memory fault from ssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337019#M190014</link>
      <description>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&lt;BR /&gt;&lt;BR /&gt;file core should yield memory fault / sigsegv ....</description>
      <pubDate>Wed, 21 Jul 2004 09:07:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-fault-from-ssh/m-p/3337019#M190014</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2004-07-21T09:07:55Z</dc:date>
    </item>
  </channel>
</rss>

