<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Token Security on Nalar</title>
    <link>https://nalar.dev/tags/token-security/</link>
    <description>Recent content in Token Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/token-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Treat Signed URLs as Bearer Capabilities</title>
      <link>https://nalar.dev/treat-signed-urls-as-bearer-capabilities/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/treat-signed-urls-as-bearer-capabilities/</guid>
      <description>&lt;p&gt;A signed URL can make private content easy to share. Instead of requiring the recipient to authenticate to the storage service, an application creates a URL containing enough authorization information for the service to accept a specific request.&lt;/p&gt;&#xA;&lt;p&gt;That convenience changes the security model. Anyone who obtains a usable copy of the URL may be able to exercise the authority it carries. If the URL permits too much, remains valid too long, or is exposed through logs and messages, a small disclosure can become unintended access.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
