<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Login Throttling on Nalar</title>
    <link>https://nalar.dev/tags/login-throttling/</link>
    <description>Recent content in Login Throttling on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/login-throttling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Slow Down Automated Login Attacks</title>
      <link>https://nalar.dev/slow-down-automated-login-attacks/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/slow-down-automated-login-attacks/</guid>
      <description>&lt;p&gt;A password login endpoint has to accept attempts from people who sometimes mistype their passwords. The same property also gives automated clients a place to try many guesses. If the application processes every attempt at full speed, an attacker can repeatedly test passwords against one account or spread attempts across many accounts.&lt;/p&gt;&#xA;&lt;p&gt;A correct password hash does not solve this problem. Password hashing makes each password verification deliberately costly, but the server still has to decide how many online attempts it will accept. Without another control, the application may provide an attacker with a large number of guesses over time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
