<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Identity on Nalar</title>
    <link>https://nalar.dev/tags/identity/</link>
    <description>Recent content in Identity on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/identity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design User Identifiers to Resist Visual Spoofing</title>
      <link>https://nalar.dev/design-user-identifiers-to-resist-visual-spoofing/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/design-user-identifiers-to-resist-visual-spoofing/</guid>
      <description>&lt;p&gt;Two account identifiers can be different to software while looking almost identical to a person. That gap matters anywhere people use a displayed identifier to decide whom they are trusting: administrator consoles, collaboration tools, package registries, marketplaces, support systems, or internal approval workflows.&lt;/p&gt;&#xA;&lt;p&gt;If an application treats visual appearance as irrelevant, an attacker may be able to register an identifier that resembles a trusted account closely enough to mislead another user. The database still sees two distinct strings. The human may not.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
