<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Secrets-Management on Thibaut Tauveron</title>
    <link>https://blog.tauveron.com/tags/secrets-management/</link>
    <description>Recent content in Secrets-Management on Thibaut Tauveron</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 29 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.tauveron.com/tags/secrets-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The security model behind a secret-sharing link</title>
      <link>https://blog.tauveron.com/the-security-model-behind-a-secret-sharing-link/</link>
      <pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.tauveron.com/the-security-model-behind-a-secret-sharing-link/</guid>
      <description>&lt;h1 id=&#34;1-the-link-as-a-security-object&#34;&gt;1. The link as a security object &lt;a href=&#34;#1-the-link-as-a-security-object&#34; class=&#34;anchor&#34;&gt;🔗&lt;/a&gt;&lt;/h1&gt;&lt;p&gt;I recently built psst-rs, a small secret-sharing service written in Rust.The goal is simple: paste a small secret, generate a link, send the link to someone, and let the secret be read only once.&lt;/p&gt;&#xA;&lt;p&gt;A secret-sharing link is not a normal link. It does two things: It points to the encrypted secret and it carries the key needed to decrypt it.&lt;/p&gt;&#xA;&lt;p&gt;In psst-rs, the server never sees the key: the secret is encrypted in the browser with AES-GCM. The server receives only the ciphertext and the nonce, the key remains in the URL after #.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
