<?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: sshd in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524320#M745501</link>
    <description>Is this from same host??&lt;BR /&gt;&lt;BR /&gt;type ssh&lt;BR /&gt;what ssh&lt;BR /&gt;type sshd&lt;BR /&gt;what sshd&lt;BR /&gt;</description>
    <pubDate>Wed, 13 Apr 2005 13:00:06 GMT</pubDate>
    <dc:creator>RAC_1</dc:creator>
    <dc:date>2005-04-13T13:00:06Z</dc:date>
    <item>
      <title>sshd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524319#M745500</link>
      <description>We are experienceing some weirdness with sshd.&lt;BR /&gt;When executing ssh -V we get a response of OpenSSH_3.8.1p1, OpenSSL 0.9.7d, when testing sshd we telnet (hostname) 22 the response we get is SSH-2.0-OpenSSH_3.6p1. We have searched the system for any and all sshd executables and only fine one under /usr/local/sbin/sshd, the init script also points to this exe. Anyway, this is causing the system not to disable a user account with multiple login attempts (trusted).&lt;BR /&gt;Is there a way to find out why we are getting two different outputs vers for sshd?&lt;BR /&gt;Thanks&lt;BR /&gt;S</description>
      <pubDate>Wed, 13 Apr 2005 12:55:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524319#M745500</guid>
      <dc:creator>Stu Innes</dc:creator>
      <dc:date>2005-04-13T12:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: sshd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524320#M745501</link>
      <description>Is this from same host??&lt;BR /&gt;&lt;BR /&gt;type ssh&lt;BR /&gt;what ssh&lt;BR /&gt;type sshd&lt;BR /&gt;what sshd&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Apr 2005 13:00:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524320#M745501</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2005-04-13T13:00:06Z</dc:date>
    </item>
    <item>
      <title>Re: sshd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524321#M745502</link>
      <description>Might be that sshd was build with a STATIC libssh&lt;BR /&gt;This is rare&lt;BR /&gt;&lt;BR /&gt;Then there is the - more likely - possibility that there are more than one sshd available, and the system starts one you don't expect&lt;BR /&gt;when you're connected, use lsof to see what files the sshd process has open&lt;BR /&gt;&lt;BR /&gt;Or find sshd system wide&lt;BR /&gt;&lt;BR /&gt;Or remove all (open)ssh/(open)ssl packages you can find and install the most recent version available&lt;BR /&gt;&lt;BR /&gt;FWIW openssh-4.0p1 is MUCH faster than openssh-3.9.x&lt;BR /&gt;&lt;BR /&gt;Enjoy, Have FUN! H.Merijn</description>
      <pubDate>Wed, 13 Apr 2005 13:20:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524321#M745502</guid>
      <dc:creator>H.Merijn Brand (procura</dc:creator>
      <dc:date>2005-04-13T13:20:26Z</dc:date>
    </item>
    <item>
      <title>Re: sshd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524322#M745503</link>
      <description>Hi Stu,&lt;BR /&gt;&lt;BR /&gt;Besides RAC's ideas also try&lt;BR /&gt;&lt;BR /&gt;ps -ef | grep sshd&lt;BR /&gt;&lt;BR /&gt;then check that the running sshd is indeed the same one that is being started up in the rcX.d script. If it's not then use /sbin/init.d/sshd2 stop &amp;amp; /sbin/init.d/sshd2 start (use the appropriate script name of course) to bounce it. It may be that someone manually started the wrong one. &lt;BR /&gt;&lt;BR /&gt;If that checks out then run&lt;BR /&gt;&lt;BR /&gt;swlist | grep -i ssh&lt;BR /&gt;&lt;BR /&gt;to verify the proper version is installed - then run&lt;BR /&gt;&lt;BR /&gt;swlist -l fileset -a state | grep -i ssh&lt;BR /&gt;&lt;BR /&gt;and verify that the filesets are *all* in a configured state. May be that the "RUN" fileset didn't install correctly or all the way.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Jeff</description>
      <pubDate>Wed, 13 Apr 2005 13:34:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524322#M745503</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2005-04-13T13:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: sshd</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524323#M745504</link>
      <description>Stu,&lt;BR /&gt;&lt;BR /&gt;Check the /etc/rc.config.d/sshd file.&lt;BR /&gt;To which directory is it pointing?&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;&lt;BR /&gt;Darrel</description>
      <pubDate>Wed, 13 Apr 2005 14:07:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sshd/m-p/3524323#M745504</guid>
      <dc:creator>Darrel Louis</dc:creator>
      <dc:date>2005-04-13T14:07:34Z</dc:date>
    </item>
  </channel>
</rss>

