<?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: Security Access in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537206#M595028</link>
    <description>Also remember to read the man pages.  These are not written for rocket scientists, and are handy on all platforms.&lt;BR /&gt;&amp;gt;man inetd.sec&lt;BR /&gt;will give you plenty of information, and examples on building the file correctly, even tell you to run inetd -c to implement the changes while inetd is running.&lt;BR /&gt;&lt;BR /&gt;Reading about bastion hosts, and C2 security is fine, but not really practical for a newbie.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Shannon</description>
    <pubDate>Thu, 07 Jun 2001 14:10:37 GMT</pubDate>
    <dc:creator>Shannon Petry</dc:creator>
    <dc:date>2001-06-07T14:10:37Z</dc:date>
    <item>
      <title>Security Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537200#M595022</link>
      <description>I want to disable all the R's (remsh, rlogin, rcp and etc) on my server and allow certain i.p.  address to acces my server.  I tried to set up up in file /var/adm/inetd.sec but must have not implement it correctly.   I need some assistance.   Also do anyone know a good web site that talk about security issues and patching up your server against hackers.</description>
      <pubDate>Wed, 06 Jun 2001 14:54:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537200#M595022</guid>
      <dc:creator>Ray Bell</dc:creator>
      <dc:date>2001-06-06T14:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: Security Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537201#M595023</link>
      <description>For info of inetd see:&lt;BR /&gt;&lt;A href="http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90685/B2355-90685_top.html&amp;amp;con=/hpux/onlinedocs/B2355-90685/00/00/10-con.html&amp;amp;toc=/hpux/onlinedocs/B2355-90685/00/00/10-toc.html&amp;amp;searchterms=inetd&amp;amp;queryid=20010606-085725" target="_blank"&gt;http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90685/B2355-90685_top.html&amp;amp;con=/hpux/onlinedocs/B2355-90685/00/00/10-con.html&amp;amp;toc=/hpux/onlinedocs/B2355-90685/00/00/10-toc.html&amp;amp;searchterms=inetd&amp;amp;queryid=20010606-085725&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;see also IPSEC:&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/J4255-90005/J4255-90005.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/J4255-90005/J4255-90005.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Jun 2001 15:00:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537201#M595023</guid>
      <dc:creator>Vincenzo Restuccia</dc:creator>
      <dc:date>2001-06-06T15:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: Security Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537202#M595024</link>
      <description>Hi Ray:&lt;BR /&gt;&lt;BR /&gt;Here's one specifically for HP-UX, for starters:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://secinf.net/info/unix/secureHP-UX.html" target="_blank"&gt;http://secinf.net/info/unix/secureHP-UX.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 06 Jun 2001 15:02:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537202#M595024</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-06-06T15:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: Security Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537203#M595025</link>
      <description>Ray, the inetd.sec file should be composed of lines like:&lt;BR /&gt;&lt;BR /&gt;telnet  allow   192.168.* &lt;BR /&gt;rlogin  allow   *.mynetwork.net&lt;BR /&gt;&lt;BR /&gt;or you can tool it down to a particular host.&lt;BR /&gt;&lt;BR /&gt;Happy locking down...</description>
      <pubDate>Wed, 06 Jun 2001 21:39:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537203#M595025</guid>
      <dc:creator>Mark Fenton</dc:creator>
      <dc:date>2001-06-06T21:39:44Z</dc:date>
    </item>
    <item>
      <title>Re: Security Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537204#M595026</link>
      <description>There is a document on building a bastion host that is very comprehensive...and is a good starting place.  It does cover disabling the r* and many other things for hp.&lt;BR /&gt;For 11.X&lt;BR /&gt;&lt;A href="http://people.hp.se/stevesk/bastion11.html" target="_blank"&gt;http://people.hp.se/stevesk/bastion11.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For 10.X&lt;BR /&gt;&lt;A href="http://people.hp.se/stevesk/bastion10.html" target="_blank"&gt;http://people.hp.se/stevesk/bastion10.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The security forum has many good things as well just do searches for topics and you should find good info as well as references to sites for public domain code, etc.&lt;BR /&gt;&lt;BR /&gt;The previous references are great starting points as well for HP security.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Peggy</description>
      <pubDate>Thu, 07 Jun 2001 12:55:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537204#M595026</guid>
      <dc:creator>Peggy Fong</dc:creator>
      <dc:date>2001-06-07T12:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Security Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537205#M595027</link>
      <description>BTW&lt;BR /&gt;If you want to completely disable the r* services (rcp, remsh, rlogin..) and only allow telnet, then you need to comment them out of /etc/inetd.conf and then re-read the file by running 'inetd -c'&lt;BR /&gt;&lt;BR /&gt;Then use inetd.sec to allow telnet from certain subnets or ip addresses....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Peggy</description>
      <pubDate>Thu, 07 Jun 2001 12:57:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537205#M595027</guid>
      <dc:creator>Peggy Fong</dc:creator>
      <dc:date>2001-06-07T12:57:29Z</dc:date>
    </item>
    <item>
      <title>Re: Security Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537206#M595028</link>
      <description>Also remember to read the man pages.  These are not written for rocket scientists, and are handy on all platforms.&lt;BR /&gt;&amp;gt;man inetd.sec&lt;BR /&gt;will give you plenty of information, and examples on building the file correctly, even tell you to run inetd -c to implement the changes while inetd is running.&lt;BR /&gt;&lt;BR /&gt;Reading about bastion hosts, and C2 security is fine, but not really practical for a newbie.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Shannon</description>
      <pubDate>Thu, 07 Jun 2001 14:10:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-access/m-p/2537206#M595028</guid>
      <dc:creator>Shannon Petry</dc:creator>
      <dc:date>2001-06-07T14:10:37Z</dc:date>
    </item>
  </channel>
</rss>

