<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Credential Attacks on Nalar</title>
    <link>https://nalar.dev/tags/credential-attacks/</link>
    <description>Recent content in Credential Attacks on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/credential-attacks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Throttle Authentication Attempts Without Locking Out Users</title>
      <link>https://nalar.dev/throttle-authentication-attempts-without-locking-out-users/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/throttle-authentication-attempts-without-locking-out-users/</guid>
      <description>&lt;p&gt;Password authentication exposes a public decision point: a client submits a claimed identity and a secret, then the server accepts or rejects the pair. Attackers can automate that decision point at a scale no human user can match.&lt;/p&gt;&#xA;&lt;p&gt;A simple request limit helps, but authentication traffic has unusual constraints. A limit tied only to an IP address can punish thousands of legitimate users behind one gateway. A limit tied only to an account lets an attacker deliberately block a victim from signing in. A permanent account lock can turn a guessing defense into a denial-of-service primitive.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
