<?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: rexec in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108270#M631633</link>
    <description>Hi Ihab,&lt;BR /&gt; &lt;BR /&gt;Another option would be to obtain &amp;amp; install Tcp_wrappers software. Using it's /etc/hosts.allow &amp;amp; /etc/hosts.deny files granularity can be taken down to the user level as well as host &amp;amp; subnet levels.&lt;BR /&gt;&lt;BR /&gt;Tcp_wrappers can be obtained here:&lt;BR /&gt; &lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/tcp_wrappers-7.6/" target="_blank"&gt;http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/tcp_wrappers-7.6/&lt;/A&gt;&lt;BR /&gt; &lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
    <pubDate>Mon, 03 Nov 2003 08:57:23 GMT</pubDate>
    <dc:creator>Jeff Schussele</dc:creator>
    <dc:date>2003-11-03T08:57:23Z</dc:date>
    <item>
      <title>rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108263#M631626</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;Is there a way to ban only one user from using rexec.&lt;BR /&gt;&lt;BR /&gt;I know that I can comment the 'exec' line in /etc/inetd.conf but this will ban all users.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Ihab</description>
      <pubDate>Mon, 03 Nov 2003 01:53:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108263#M631626</guid>
      <dc:creator>Ihab Zaki</dc:creator>
      <dc:date>2003-11-03T01:53:47Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108264#M631627</link>
      <description>You can use /var/adm/inetd.sec to limit individual IP's and hosts from running services.&lt;BR /&gt; &lt;BR /&gt;It will look something like the following but check out "man inetd.sec"&lt;BR /&gt; &lt;BR /&gt;exec      deny    10.0.8.231</description>
      <pubDate>Mon, 03 Nov 2003 01:58:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108264#M631627</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-11-03T01:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108265#M631628</link>
      <description>Further to Mark's suggestion, note that you will have to modify the inetd.sec file on each remote system you want to stop the user getting out to.&lt;BR /&gt;&lt;BR /&gt;You could consider writing a wrapper for rexec on the local system, but it's not so clean a solution.&lt;BR /&gt;&lt;BR /&gt;-- Graham</description>
      <pubDate>Mon, 03 Nov 2003 03:16:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108265#M631628</guid>
      <dc:creator>Graham Cameron_1</dc:creator>
      <dc:date>2003-11-03T03:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108266#M631629</link>
      <description>This applies to host / IP but not to user level, in my case I want to ban a user not a machine</description>
      <pubDate>Mon, 03 Nov 2003 06:46:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108266#M631629</guid>
      <dc:creator>Ihab Zaki</dc:creator>
      <dc:date>2003-11-03T06:46:18Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108267#M631630</link>
      <description>You can do this but it's going to be really annoying. You can make sure that each user that uses rexec has a .rhosts file except the one you want to stop and that /etc/hosts.equiv does not contain a reference to the originating host.&lt;BR /&gt; &lt;BR /&gt;This is going to be a pain to manage if you have a lot of users using rexec.</description>
      <pubDate>Mon, 03 Nov 2003 08:39:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108267#M631630</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-11-03T08:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108268#M631631</link>
      <description>I don't think the suggestion re .rhosts will help.&lt;BR /&gt;Unlike remsh, rexec dies not use .rhosts (or hosts.equiv). It prompts for a password and uses login authentication.&lt;BR /&gt;&lt;BR /&gt;-- Graham</description>
      <pubDate>Mon, 03 Nov 2003 08:53:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108268#M631631</guid>
      <dc:creator>Graham Cameron_1</dc:creator>
      <dc:date>2003-11-03T08:53:40Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108269#M631632</link>
      <description>Graham,&lt;BR /&gt; &lt;BR /&gt;"man rexec"</description>
      <pubDate>Mon, 03 Nov 2003 08:56:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108269#M631632</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-11-03T08:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108270#M631633</link>
      <description>Hi Ihab,&lt;BR /&gt; &lt;BR /&gt;Another option would be to obtain &amp;amp; install Tcp_wrappers software. Using it's /etc/hosts.allow &amp;amp; /etc/hosts.deny files granularity can be taken down to the user level as well as host &amp;amp; subnet levels.&lt;BR /&gt;&lt;BR /&gt;Tcp_wrappers can be obtained here:&lt;BR /&gt; &lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/tcp_wrappers-7.6/" target="_blank"&gt;http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/tcp_wrappers-7.6/&lt;/A&gt;&lt;BR /&gt; &lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Mon, 03 Nov 2003 08:57:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108270#M631633</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2003-11-03T08:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: rexec</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108271#M631634</link>
      <description>Graham,&lt;BR /&gt; &lt;BR /&gt;Apologies!! You are right, it's a long time since I read the man page for "rexec".&lt;BR /&gt; &lt;BR /&gt;rexec authenticates the same as login!</description>
      <pubDate>Mon, 03 Nov 2003 08:59:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rexec/m-p/3108271#M631634</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-11-03T08:59:33Z</dc:date>
    </item>
  </channel>
</rss>

