<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Privacy on Nalar</title>
    <link>https://nalar.dev/tags/privacy/</link>
    <description>Recent content in Privacy on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/privacy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reduce Account Enumeration with Consistent Authentication Responses</title>
      <link>https://nalar.dev/reduce-account-enumeration-with-consistent-authentication-responses/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/reduce-account-enumeration-with-consistent-authentication-responses/</guid>
      <description>&lt;p&gt;A login form can reject every incorrect password and still reveal useful information about its users. If the application says &lt;code&gt;Account not found&lt;/code&gt; for one email address and &lt;code&gt;Wrong password&lt;/code&gt; for another, anyone who can submit login attempts can learn which address belongs to an account.&lt;/p&gt;&#xA;&lt;p&gt;That information leak is called &lt;strong&gt;account enumeration&lt;/strong&gt;. The same problem can appear in password-reset, registration, invitation, and account-recovery flows. Even when the visible message is identical, differences in HTTP responses, redirects, response size, or processing time can reveal the same fact.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
