<?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 issues / configuration in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063886#M437334</link>
    <description>Not possible in an untrusted environment.&lt;BR /&gt;&lt;BR /&gt;In a trusted environment, this is controlled by security policies, which can be seen via the getprpw command ('man getprpw' for more info).  This is NOT configurable in the /etc/default/security file.  &lt;BR /&gt;&lt;BR /&gt;You should do a 'man security' for information on the security file.&lt;BR /&gt;</description>
    <pubDate>Mon, 20 Aug 2007 08:45:04 GMT</pubDate>
    <dc:creator>Patrick Wallek</dc:creator>
    <dc:date>2007-08-20T08:45:04Z</dc:date>
    <item>
      <title>security issues / configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063885#M437333</link>
      <description>hi.&lt;BR /&gt;&lt;BR /&gt;i wonder how i can lock a useraccount after a certain amount of failed logins in a UNTRUSTED system.. like /usr/lbin/modprpw -m umaxlntr=6 "$logname" is in trusted.&lt;BR /&gt;&lt;BR /&gt;i also wonder what the string in /etc/default/security should be to make it global in a TRUSTED system..&lt;BR /&gt;&lt;BR /&gt;anyone?&lt;BR /&gt;&lt;BR /&gt;regards &lt;BR /&gt;pål</description>
      <pubDate>Mon, 20 Aug 2007 08:23:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063885#M437333</guid>
      <dc:creator>Paul Torp</dc:creator>
      <dc:date>2007-08-20T08:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: security issues / configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063886#M437334</link>
      <description>Not possible in an untrusted environment.&lt;BR /&gt;&lt;BR /&gt;In a trusted environment, this is controlled by security policies, which can be seen via the getprpw command ('man getprpw' for more info).  This is NOT configurable in the /etc/default/security file.  &lt;BR /&gt;&lt;BR /&gt;You should do a 'man security' for information on the security file.&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Aug 2007 08:45:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063886#M437334</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2007-08-20T08:45:04Z</dc:date>
    </item>
    <item>
      <title>Re: security issues / configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063887#M437335</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;On a non-trusted system you would need to look at this output.&lt;BR /&gt;lastb -R&lt;BR /&gt;&lt;BR /&gt;You can run a cron script that checks this output user by user. At this point when you find three bad logins you can issue a passwd -l username command.&lt;BR /&gt;&lt;BR /&gt;There is a script posted in the sysadmin scripts thread that does exactly this.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=51050" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=51050&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Aug 2007 08:58:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063887#M437335</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-08-20T08:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: security issues / configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063888#M437336</link>
      <description>hi..&lt;BR /&gt;&lt;BR /&gt;i have tried looking for that script in section 2 and 3.. (of favorite scripts) but cant really find it..&lt;BR /&gt;&lt;BR /&gt;i am running out of time and got deadline tomorrow to come up with something to solve the issue..&lt;BR /&gt;&lt;BR /&gt;pal</description>
      <pubDate>Tue, 21 Aug 2007 03:28:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063888#M437336</guid>
      <dc:creator>Paul Torp</dc:creator>
      <dc:date>2007-08-21T03:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: security issues / configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063889#M437337</link>
      <description>the sad sad thing is that i have no hpux boxes to test on atm..  (not even a production).. makes things a  bit harder...</description>
      <pubDate>Tue, 21 Aug 2007 03:35:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063889#M437337</guid>
      <dc:creator>Paul Torp</dc:creator>
      <dc:date>2007-08-21T03:35:14Z</dc:date>
    </item>
    <item>
      <title>Re: security issues / configuration</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063890#M437338</link>
      <description>found it SEP..&lt;BR /&gt;&lt;BR /&gt;tnx</description>
      <pubDate>Tue, 21 Aug 2007 04:20:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/security-issues-configuration/m-p/5063890#M437338</guid>
      <dc:creator>Paul Torp</dc:creator>
      <dc:date>2007-08-21T04:20:20Z</dc:date>
    </item>
  </channel>
</rss>

