<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PASETO on Nalar</title>
    <link>https://nalar.dev/tags/paseto/</link>
    <description>Recent content in PASETO on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/paseto/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PASETO Public and Local Tokens Do Not Solve Session Revocation</title>
      <link>https://nalar.dev/paseto-public-local-tokens-do-not-solve-session-revocation/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/paseto-public-local-tokens-do-not-solve-session-revocation/</guid>
      <description>&lt;p&gt;A PASETO token can protect claims cryptographically without knowing whether the user has logged out. That boundary matters more than the usual JWT-versus-PASETO comparison: changing the token format does not create session revocation.&lt;/p&gt;&#xA;&lt;p&gt;PASETO gives each token an explicit version and purpose. With Version 4, &lt;code&gt;v4.public&lt;/code&gt; signs a message with Ed25519, while &lt;code&gt;v4.local&lt;/code&gt; encrypts and authenticates a message with symmetric cryptography. Those choices determine who can read a token and who can create or verify it. They do not determine whether a previously valid token should still be accepted after a session changes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
