<?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: How to Lock and Unlock User After Failed SSH Logins	</title>
	<atom:link href="https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Wed, 09 Apr 2025 04:27:15 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Ravi Saive		</title>
		<link>https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/comment-page-1/#comment-2293929</link>

		<dc:creator><![CDATA[Ravi Saive]]></dc:creator>
		<pubDate>Wed, 09 Apr 2025 04:27:15 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=27613#comment-2293929</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/comment-page-1/#comment-2293885&quot;&gt;atomick&lt;/a&gt;.

@Atomick,

Great tip - thanks for sharing! 

&lt;strong&gt;pam_tally&lt;/strong&gt; and &lt;strong&gt;pam_tally2&lt;/strong&gt; are definitely handy tools for handling SSH lockouts, especially on systems using older PAM modules. Creating a small script with &lt;code&gt;$1&lt;/code&gt; as a placeholder for the username is a smart way to save time.

And yes, as you said, the effectiveness can depend on the system’s PAM setup — always good to double-check the config.

Appreciate your input!]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/comment-page-1/#comment-2293885">atomick</a>.</p>
<p>@Atomick,</p>
<p>Great tip &#8211; thanks for sharing! </p>
<p><strong>pam_tally</strong> and <strong>pam_tally2</strong> are definitely handy tools for handling SSH lockouts, especially on systems using older PAM modules. Creating a small script with <code>$1</code> as a placeholder for the username is a smart way to save time.</p>
<p>And yes, as you said, the effectiveness can depend on the system’s PAM setup — always good to double-check the config.</p>
<p>Appreciate your input!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: atomick		</title>
		<link>https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/comment-page-1/#comment-2293885</link>

		<dc:creator><![CDATA[atomick]]></dc:creator>
		<pubDate>Wed, 09 Apr 2025 03:04:26 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=27613#comment-2293885</guid>

					<description><![CDATA[You could also check out pam_tally and pam_tally2, which can help reset SSH block and lock counters.

For example, use:
&lt;pre&gt;
sudo pam_tally --reset --user $1
sudo pam_tally2 --reset --user $1
&lt;/pre&gt;
You can even create a short Bash script using a wildcard like $1 to pass the locked username as a parameter.

Example:
&lt;pre&gt;
sudo pam_tally --reset --user JohnDoe
&lt;/pre&gt;
This is another useful way to handle account lockouts. All related options might depend on the PAM configuration on your system.]]></description>
			<content:encoded><![CDATA[<p>You could also check out pam_tally and pam_tally2, which can help reset SSH block and lock counters.</p>
<p>For example, use:</p>
<pre>
sudo pam_tally --reset --user $1
sudo pam_tally2 --reset --user $1
</pre>
<p>You can even create a short Bash script using a wildcard like $1 to pass the locked username as a parameter.</p>
<p>Example:</p>
<pre>
sudo pam_tally --reset --user JohnDoe
</pre>
<p>This is another useful way to handle account lockouts. All related options might depend on the PAM configuration on your system.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Amar Nayak		</title>
		<link>https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/comment-page-1/#comment-2021140</link>

		<dc:creator><![CDATA[Amar Nayak]]></dc:creator>
		<pubDate>Thu, 01 Jun 2023 04:29:21 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=27613#comment-2021140</guid>

					<description><![CDATA[Thanks for the very helpful article...

I see lots of SSH failed login attempts on my Linux server logs daily, I hope with this solution I can completely block such login attempts and secure my SSH box from unwanted authentications...]]></description>
			<content:encoded><![CDATA[<p>Thanks for the very helpful article&#8230;</p>
<p>I see lots of SSH failed login attempts on my Linux server logs daily, I hope with this solution I can completely block such login attempts and secure my SSH box from unwanted authentications&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: bread of wakanda		</title>
		<link>https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/comment-page-1/#comment-1241796</link>

		<dc:creator><![CDATA[bread of wakanda]]></dc:creator>
		<pubDate>Wed, 11 Sep 2019 05:21:02 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=27613#comment-1241796</guid>

					<description><![CDATA[what if i have a user who keeps entering the wrong password and keeps getting locked and every single day i have to unlock him .. is there any way by which i can keep that specific user out of pam policy so that he never gets locked but others can get locked?]]></description>
			<content:encoded><![CDATA[<p>what if i have a user who keeps entering the wrong password and keeps getting locked and every single day i have to unlock him .. is there any way by which i can keep that specific user out of pam policy so that he never gets locked but others can get locked?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Akio Crimson		</title>
		<link>https://www.tecmint.com/lock-failed-ssh-login-attempts-linux/comment-page-1/#comment-1108814</link>

		<dc:creator><![CDATA[Akio Crimson]]></dc:creator>
		<pubDate>Wed, 06 Mar 2019 20:52:22 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=27613#comment-1108814</guid>

					<description><![CDATA[Thanks for this info. I had to come up with something because when I logged in today, it said there were &lt;strong&gt;43,945&lt;/strong&gt; failed login attempts to root. So clearly someone set up a server in china to try to brute force their way in. I set the &lt;strong&gt;unlock_time&lt;/strong&gt; in mine to 24 hours after 2 failed attempts.]]></description>
			<content:encoded><![CDATA[<p>Thanks for this info. I had to come up with something because when I logged in today, it said there were <strong>43,945</strong> failed login attempts to root. So clearly someone set up a server in china to try to brute force their way in. I set the <strong>unlock_time</strong> in mine to 24 hours after 2 failed attempts.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
