<?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 User does not locked in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/user-does-not-locked/m-p/6113801#M54352</link>
    <description>&lt;P&gt;I have this configuration on the server:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;#&amp;nbsp; cat /etc/pam.d/system-auth&lt;BR /&gt;#%PAM-1.0&lt;BR /&gt;# This file is auto-generated.&lt;BR /&gt;# User changes will be destroyed the next time authconfig is run.&lt;/P&gt;&lt;P&gt;auth required pam_env.so&lt;BR /&gt;auth required pam_tally2.so deny=3 onerr=fail&lt;BR /&gt;auth sufficient pam_unix.so try_first_pass&lt;BR /&gt;auth required pam_deny.so&lt;/P&gt;&lt;P&gt;account required pam_unix.so&lt;BR /&gt;account required pam_tally2.so&lt;BR /&gt;account required pam_permit.so&lt;/P&gt;&lt;P&gt;password required pam_cracklib.so retry=3 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1 minlen=8&lt;BR /&gt;password sufficient pam_unix.so md5 shadow try_first_pass use_authtok remember=10&lt;BR /&gt;password required pam_deny.so&lt;/P&gt;&lt;P&gt;session required pam_limits.so&lt;BR /&gt;session [success=1 default=ignore] pam_succeed_if.so service in crond quiet&lt;BR /&gt;session required pam_unix.so&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;With: Red Hat Enterprise Linux Server release 5.8&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this configuration with deny=3, when one user put 3 wrong passwd the user locked.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It it possible to do that one user doesn't locked if they put 3 wrongs passwd?&lt;BR /&gt;How I do it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot of!&lt;/P&gt;&lt;P&gt;Carmen.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jun 2013 10:19:49 GMT</pubDate>
    <dc:creator>Carme Torca</dc:creator>
    <dc:date>2013-06-25T10:19:49Z</dc:date>
    <item>
      <title>User does not locked</title>
      <link>https://community.hpe.com/t5/operating-system-linux/user-does-not-locked/m-p/6113801#M54352</link>
      <description>&lt;P&gt;I have this configuration on the server:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;#&amp;nbsp; cat /etc/pam.d/system-auth&lt;BR /&gt;#%PAM-1.0&lt;BR /&gt;# This file is auto-generated.&lt;BR /&gt;# User changes will be destroyed the next time authconfig is run.&lt;/P&gt;&lt;P&gt;auth required pam_env.so&lt;BR /&gt;auth required pam_tally2.so deny=3 onerr=fail&lt;BR /&gt;auth sufficient pam_unix.so try_first_pass&lt;BR /&gt;auth required pam_deny.so&lt;/P&gt;&lt;P&gt;account required pam_unix.so&lt;BR /&gt;account required pam_tally2.so&lt;BR /&gt;account required pam_permit.so&lt;/P&gt;&lt;P&gt;password required pam_cracklib.so retry=3 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1 minlen=8&lt;BR /&gt;password sufficient pam_unix.so md5 shadow try_first_pass use_authtok remember=10&lt;BR /&gt;password required pam_deny.so&lt;/P&gt;&lt;P&gt;session required pam_limits.so&lt;BR /&gt;session [success=1 default=ignore] pam_succeed_if.so service in crond quiet&lt;BR /&gt;session required pam_unix.so&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;With: Red Hat Enterprise Linux Server release 5.8&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this configuration with deny=3, when one user put 3 wrong passwd the user locked.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It it possible to do that one user doesn't locked if they put 3 wrongs passwd?&lt;BR /&gt;How I do it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot of!&lt;/P&gt;&lt;P&gt;Carmen.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2013 10:19:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/user-does-not-locked/m-p/6113801#M54352</guid>
      <dc:creator>Carme Torca</dc:creator>
      <dc:date>2013-06-25T10:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: User does not locked</title>
      <link>https://community.hpe.com/t5/operating-system-linux/user-does-not-locked/m-p/6114923#M54353</link>
      <description>&lt;P&gt;Your configuration actually already has a good example in it:&lt;/P&gt;&lt;PRE&gt;session [success=1 default=ignore] pam_succeed_if.so service in crond quiet&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;This line will skip the next rule if the pam_succeed_if.so conditions match, otherwise it will do nothing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So add a line just before the "auth ... pam_tally2.so" line, like this:&lt;/P&gt;&lt;PRE&gt;[...]
auth  [success=1 default=ignore] pam_succeed_if.so user in someuser quiet
auth required pam_tally2.so deny=3 onerr=fail
[...]&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you need to exclude more than one user from pam_tally2 processing, you can use a colon-separated list of usernames,&lt;/P&gt;&lt;P&gt;like this: "...pam_succeed_if.so user in user1:user2:user3".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or you can create a group (for example "nolock") and set the pam_succeed_if condition like this: "... pam_succeed_if.so user ingroup nolock". Then add the users that should not be locked by pam_tally2 to the "nolock" group.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2013 05:07:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/user-does-not-locked/m-p/6114923#M54353</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2013-06-26T05:07:29Z</dc:date>
    </item>
  </channel>
</rss>

