<?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 protocol on OpenVMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848016#M52842</link>
    <description>The PC client vendor has acknowledged the problem and will be issuing a patch.  Thanks for the help.</description>
    <pubDate>Mon, 28 Aug 2006 10:21:26 GMT</pubDate>
    <dc:creator>Thomas A. Williams</dc:creator>
    <dc:date>2006-08-28T10:21:26Z</dc:date>
    <item>
      <title>SSH protocol on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848013#M52839</link>
      <description>We've got a problem with a PC client not handling an expired password correctly.  The PC client vendor has said the following:&lt;BR /&gt;&lt;BR /&gt;" think that Extra! is not supporting the input_userrauth_passwd_changereq OpenVMS SSH Server command, because OpenVMS SSH Server is not based on OpenSSH standards, but it is based on SSH2 Software from a company called SSH Communications Security. "&lt;BR /&gt;&lt;BR /&gt;Question:  Is what they say true - SSH on OpenVMS is NOT based on OpenSSH?  &lt;BR /&gt;&lt;BR /&gt;And is the "input_userrauth_passwd_changereq" signal non-standard?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Tue, 22 Aug 2006 07:55:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848013#M52839</guid>
      <dc:creator>Thomas A. Williams</dc:creator>
      <dc:date>2006-08-22T07:55:40Z</dc:date>
    </item>
    <item>
      <title>Re: SSH protocol on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848014#M52840</link>
      <description>&amp;gt; [...] SSH on OpenVMS is NOT based on OpenSSH? &lt;BR /&gt;&lt;BR /&gt;True enough.  For example, the key file&lt;BR /&gt;formats differ.  (Search this forum for&lt;BR /&gt;"ssh-keygen".)&lt;BR /&gt;&lt;BR /&gt;But that doesn't imply that it's defective.&lt;BR /&gt;&lt;BR /&gt;I know nothing specific about what happens&lt;BR /&gt;with an expired password.</description>
      <pubDate>Tue, 22 Aug 2006 09:46:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848014#M52840</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2006-08-22T09:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: SSH protocol on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848015#M52841</link>
      <description>The SSH_MSG_USERAUTH_PASSWD_CHANGEREQ is defined in RFC 4252.  The language describing it uses a lot of "SHOULD" and "MAY", so it should be considered an optional part of the protocol, not a mandatory part of the protocol.&lt;BR /&gt;&lt;BR /&gt;OpenSSH does not define the standard.  The RFCs do.</description>
      <pubDate>Mon, 28 Aug 2006 09:33:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848015#M52841</guid>
      <dc:creator>Richard Whalen</dc:creator>
      <dc:date>2006-08-28T09:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSH protocol on OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848016#M52842</link>
      <description>The PC client vendor has acknowledged the problem and will be issuing a patch.  Thanks for the help.</description>
      <pubDate>Mon, 28 Aug 2006 10:21:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-protocol-on-openvms/m-p/3848016#M52842</guid>
      <dc:creator>Thomas A. Williams</dc:creator>
      <dc:date>2006-08-28T10:21:26Z</dc:date>
    </item>
  </channel>
</rss>

