<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Webcrypto on Hardcode Consulting</title>
    <link>https://blog.hardcodeconsulting.tech/tags/webcrypto/</link>
    <description>Recent content in Webcrypto on Hardcode Consulting</description>
    <image>
      <title>Hardcode Consulting</title>
      <url>https://blog.hardcodeconsulting.tech/favicon.svg</url>
      <link>https://blog.hardcodeconsulting.tech/favicon.svg</link>
    </image>
    <generator>Hugo -- 0.167.0</generator>
    <language>en</language>
    <lastBuildDate>Sun, 02 Aug 2026 18:00:00 +0530</lastBuildDate>
    <atom:link href="https://blog.hardcodeconsulting.tech/tags/webcrypto/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Signing Every Request, Not Just the Refresh</title>
      <link>https://blog.hardcodeconsulting.tech/post/signing-every-request-not-just-the-refresh/</link>
      <pubDate>Sun, 02 Aug 2026 18:00:00 +0530</pubDate>
      <guid>https://blog.hardcodeconsulting.tech/post/signing-every-request-not-just-the-refresh/</guid>
      <description>Device binding secured the token that rotates and left the one sent on every request a plain bearer secret. Closing that with a per request signature.</description>
    </item>
    <item>
      <title>Binding a Refresh Token to the Device</title>
      <link>https://blog.hardcodeconsulting.tech/post/binding-refresh-tokens-to-the-device/</link>
      <pubDate>Sun, 19 Jul 2026 18:00:00 +0530</pubDate>
      <guid>https://blog.hardcodeconsulting.tech/post/binding-refresh-tokens-to-the-device/</guid>
      <description>A refresh token anybody can replay is a bearer secret. Binding it to a non-extractable WebCrypto key makes a copied token useless on its own.</description>
    </item>
  </channel>
</rss>
