<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: RHEL 5 Failed Login Locks</title>
	<atom:link href="http://tech.kulish.com/2009/03/16/rhel-5-failed-login-locks/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech.kulish.com/2009/03/16/rhel-5-failed-login-locks/</link>
	<description>Technology Junk Drawer</description>
	<lastBuildDate>Tue, 27 Jul 2010 02:07:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: coolhandluke</title>
		<link>http://tech.kulish.com/2009/03/16/rhel-5-failed-login-locks/#comment-9</link>
		<dc:creator>coolhandluke</dc:creator>
		<pubDate>Wed, 02 Jun 2010 10:57:44 +0000</pubDate>
		<guid isPermaLink="false">http://tech.lan.side/?p=58#comment-9</guid>
		<description>[SOLVED] pam_tally.so not reseting failed logins

On a RHEL5.3 box I have my /etc/pam.d/system-auth file just like yours above, however even when a user, say usera, logs in successfully via ssh, faillog shows an incremented login failure count.
However if I login with another user, say userb (which will now have a failed login attempt even though login was successful just like usera above), and then su to usera, faillog will clear out any and all failed login attempts for usera.
It appears su will reset the account after a successful login attempt while using ssh does not. Any suggestions for getting ssh to interact with pam_tally successfully?
[SOLVED]
Not using openssh. Using Reflections for Secure IT SSH. Either it doesnt work properly with pam_tally.so or I have not configured it correctly. However the sytem-auth file provided works with openssh.</description>
		<content:encoded><![CDATA[<p>[SOLVED] pam_tally.so not reseting failed logins</p>
<p>On a RHEL5.3 box I have my /etc/pam.d/system-auth file just like yours above, however even when a user, say usera, logs in successfully via ssh, faillog shows an incremented login failure count.<br />
However if I login with another user, say userb (which will now have a failed login attempt even though login was successful just like usera above), and then su to usera, faillog will clear out any and all failed login attempts for usera.<br />
It appears su will reset the account after a successful login attempt while using ssh does not. Any suggestions for getting ssh to interact with pam_tally successfully?<br />
[SOLVED]<br />
Not using openssh. Using Reflections for Secure IT SSH. Either it doesnt work properly with pam_tally.so or I have not configured it correctly. However the sytem-auth file provided works with openssh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://tech.kulish.com/2009/03/16/rhel-5-failed-login-locks/#comment-10</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 16 Feb 2010 16:44:26 +0000</pubDate>
		<guid isPermaLink="false">http://tech.lan.side/?p=58#comment-10</guid>
		<description>RHEL 5.3 pam_tally.so not resetting failed logins

I still can&#039;t get my configuration working with openssh and pam_tally. I have it locking ok, but it will not reset on successful login. The latest version does not have the &quot;reset&quot; option as above, and instead should do it by default, and only has a &quot;no_reset&quot; option.
Worse, when a user logs in successfully, it increments the failed attempts each time! So even with successful logins they user will eventually be locked out!</description>
		<content:encoded><![CDATA[<p>RHEL 5.3 pam_tally.so not resetting failed logins</p>
<p>I still can&#8217;t get my configuration working with openssh and pam_tally. I have it locking ok, but it will not reset on successful login. The latest version does not have the &#8220;reset&#8221; option as above, and instead should do it by default, and only has a &#8220;no_reset&#8221; option.<br />
Worse, when a user logs in successfully, it increments the failed attempts each time! So even with successful logins they user will eventually be locked out!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
