<?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 using inetd and openssh in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093991#M145495</link>
    <description>Is there any way to use inetd to limit acess via openssh?</description>
    <pubDate>Wed, 15 Oct 2003 09:47:38 GMT</pubDate>
    <dc:creator>Keri Franklin</dc:creator>
    <dc:date>2003-10-15T09:47:38Z</dc:date>
    <item>
      <title>using inetd and openssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093991#M145495</link>
      <description>Is there any way to use inetd to limit acess via openssh?</description>
      <pubDate>Wed, 15 Oct 2003 09:47:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093991#M145495</guid>
      <dc:creator>Keri Franklin</dc:creator>
      <dc:date>2003-10-15T09:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: using inetd and openssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093992#M145496</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;   Yes..absoultely&lt;BR /&gt;&lt;BR /&gt;Add an entry in inetd.conf for sshd similar to the lines of telnet.&lt;BR /&gt;&lt;BR /&gt;ssh      stream tcp nowait root /usr/local/bin/sshd sshd&lt;BR /&gt;&lt;BR /&gt;Then anyone connecting to SSH will be going through inetd and sshd will be inetd on demand which will also reduced the overhead on the server. If you dont want to used telnet after enabling sshd via inted disable the same.</description>
      <pubDate>Wed, 15 Oct 2003 10:03:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093992#M145496</guid>
      <dc:creator>ramesh_6</dc:creator>
      <dc:date>2003-10-15T10:03:52Z</dc:date>
    </item>
    <item>
      <title>Re: using inetd and openssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093993#M145497</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I don't think ssh will use tcp, if so it's entry should have been in services file.</description>
      <pubDate>Wed, 15 Oct 2003 10:11:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093993#M145497</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2003-10-15T10:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: using inetd and openssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093994#M145498</link>
      <description>Pesonally I think putting things in inetd tends to increase the overhead and slows down response times.&lt;BR /&gt; &lt;BR /&gt;However, you can do this if you want.</description>
      <pubDate>Wed, 15 Oct 2003 10:14:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093994#M145498</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-10-15T10:14:48Z</dc:date>
    </item>
    <item>
      <title>Re: using inetd and openssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093995#M145499</link>
      <description>Hi Keri,&lt;BR /&gt; &lt;BR /&gt;AFAIK ssh can use tcp-wrappers to limit access - specifically the /etc/hosts.deny &amp;amp; /etc/hosts.allow files. &lt;BR /&gt;This method does not require inetd.conf or inetd.sec to be used. &lt;BR /&gt; &lt;BR /&gt;HTH,&lt;BR /&gt;Jeff</description>
      <pubDate>Wed, 15 Oct 2003 10:58:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093995#M145499</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2003-10-15T10:58:11Z</dc:date>
    </item>
    <item>
      <title>Re: using inetd and openssh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093996#M145500</link>
      <description>I'd also agree to Mark's statement that usually the overhead is bigger when a well designed server such as sshd is started through inetd, rather than run as a standalone server (which is the usual way for SSH).&lt;BR /&gt;As I understand your motivation for sshd being started by inetd is to have some sort of TCP wrapper.&lt;BR /&gt;I think you don't need this since the sshd can take care of this by itself.&lt;BR /&gt;Read the manpage of sshd(8), and especially the config file section therein.&lt;BR /&gt;Maybe what you want can be achieved through the "AllowUsers" directive in sshd_config</description>
      <pubDate>Wed, 15 Oct 2003 11:03:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/using-inetd-and-openssh/m-p/3093996#M145500</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2003-10-15T11:03:19Z</dc:date>
    </item>
  </channel>
</rss>

