<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Secret-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/secret-management/</link>
    <description>Recent content in Secret-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/secret-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted One-Time Secret Sharing: Yopass vs Password Pusher vs SnapPass</title>
      <link>https://www.pistack.xyz/posts/2026-06-07-self-hosted-secret-sharing-yopass-password-pusher-snappass/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-07-self-hosted-secret-sharing-yopass-password-pusher-snappass/</guid>
      <description>&lt;h2 id=&#34;why-self-host-your-secret-sharing&#34;&gt;Why Self-Host Your Secret Sharing?&lt;/h2&gt;&#xA;&lt;p&gt;Sending passwords, API keys, and sensitive information over email, Slack, or messaging apps is a security anti-pattern. Those messages persist indefinitely in chat logs, email archives, and backups — creating a trail of secrets scattered across multiple systems. One-time secret sharing tools solve this by generating expiring links that self-destruct after being viewed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
