<?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: SSH keygen from windows in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-keygen-from-windows/m-p/4115948#M313981</link>
    <description>Not related to the ssh-key.&lt;BR /&gt;&lt;BR /&gt;Both the ssh client and server are expected to send an identification string in the beginning of a SSH connection, to allow the identification of protocol version and/or workarounds for known bugs in some client or server versions.&lt;BR /&gt;&lt;BR /&gt;You can see the server's identification string by telnetting to the server's port 22 (the ssh port):&lt;BR /&gt;&lt;BR /&gt;$ telnet localhost 22&lt;BR /&gt;Trying...&lt;BR /&gt;Connected to localhost.&lt;BR /&gt;Escape character is '^]'.&lt;BR /&gt;SSH-2.0-OpenSSH_4.4p1-hpn12v11&lt;BR /&gt;&lt;PRESS enter="" here=""&gt;&lt;BR /&gt;Protocol mismatch.&lt;BR /&gt;Connection closed by foreign host.&lt;BR /&gt;&lt;BR /&gt;In this example, the server's identification string is "SSH-2.0-OpenSSH_4.4p1-hpn12v11". After receiving the server's identification string, the client should respond with a similar string of its own.&lt;BR /&gt;&lt;BR /&gt;Your sshd is saying that your windows-based ssh client did not offer this information.&lt;BR /&gt;&lt;BR /&gt;As you can still connect, your client obviously does not need any special workarounds at the server-side. So the message is information only.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/PRESS&gt;</description>
    <pubDate>Thu, 13 Dec 2007 08:26:43 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2007-12-13T08:26:43Z</dc:date>
    <item>
      <title>SSH keygen from windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-keygen-from-windows/m-p/4115946#M313979</link>
      <description>Dear Experts&lt;BR /&gt;&lt;BR /&gt;I'm getting the following messages in my HP-UX box(11iv1,v2 etc.) in syslog.log&lt;BR /&gt;&lt;BR /&gt;Dec 13 11:23:25 &lt;HOSTNAME&gt; sshd[16808]: Did not receive identification string from &lt;IP_ADDRESS&gt;&lt;BR /&gt;Dec 13 11:23:35 &lt;HOSTNAME&gt; sshd[16809]: Accepted password for &lt;OS_USER&gt; from &lt;IP_ADDRESS&gt; port 4575 ssh2&lt;BR /&gt;&lt;BR /&gt;That is happen when i connect from windows workstation.&lt;BR /&gt;&lt;BR /&gt;I think this is related to ssh-key. &lt;BR /&gt;&lt;BR /&gt;Can anyone tell me how can i resolve this kind of messages?&lt;BR /&gt;&lt;BR /&gt;NB. - Though the message i can connect and work as usual.&lt;/IP_ADDRESS&gt;&lt;/OS_USER&gt;&lt;/HOSTNAME&gt;&lt;/IP_ADDRESS&gt;&lt;/HOSTNAME&gt;</description>
      <pubDate>Thu, 13 Dec 2007 05:34:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-keygen-from-windows/m-p/4115946#M313979</guid>
      <dc:creator>Jeeshan</dc:creator>
      <dc:date>2007-12-13T05:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen from windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-keygen-from-windows/m-p/4115947#M313980</link>
      <description>Can you please try change the ssh port and then check.&lt;BR /&gt;BR,&lt;BR /&gt;Kapil</description>
      <pubDate>Thu, 13 Dec 2007 06:54:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-keygen-from-windows/m-p/4115947#M313980</guid>
      <dc:creator>Kapil Jha</dc:creator>
      <dc:date>2007-12-13T06:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen from windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-keygen-from-windows/m-p/4115948#M313981</link>
      <description>Not related to the ssh-key.&lt;BR /&gt;&lt;BR /&gt;Both the ssh client and server are expected to send an identification string in the beginning of a SSH connection, to allow the identification of protocol version and/or workarounds for known bugs in some client or server versions.&lt;BR /&gt;&lt;BR /&gt;You can see the server's identification string by telnetting to the server's port 22 (the ssh port):&lt;BR /&gt;&lt;BR /&gt;$ telnet localhost 22&lt;BR /&gt;Trying...&lt;BR /&gt;Connected to localhost.&lt;BR /&gt;Escape character is '^]'.&lt;BR /&gt;SSH-2.0-OpenSSH_4.4p1-hpn12v11&lt;BR /&gt;&lt;PRESS enter="" here=""&gt;&lt;BR /&gt;Protocol mismatch.&lt;BR /&gt;Connection closed by foreign host.&lt;BR /&gt;&lt;BR /&gt;In this example, the server's identification string is "SSH-2.0-OpenSSH_4.4p1-hpn12v11". After receiving the server's identification string, the client should respond with a similar string of its own.&lt;BR /&gt;&lt;BR /&gt;Your sshd is saying that your windows-based ssh client did not offer this information.&lt;BR /&gt;&lt;BR /&gt;As you can still connect, your client obviously does not need any special workarounds at the server-side. So the message is information only.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/PRESS&gt;</description>
      <pubDate>Thu, 13 Dec 2007 08:26:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-keygen-from-windows/m-p/4115948#M313981</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2007-12-13T08:26:43Z</dc:date>
    </item>
  </channel>
</rss>

