<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>E2EE</title><link>https://blog.ast.moe/en/tags/e2ee/</link><description>Recent posts: Gorimuchu</description><generator>Hugo</generator><item><title>Designing Sakura's stored data so a database leak does not expose message contents</title><link>https://blog.ast.moe/en/blog/2026-11-12/</link><pubDate>Thu, 12 Nov 2026 22:26:15 +0900</pubDate><guid>https://blog.ast.moe/en/blog/2026-11-12/</guid><description>&lt;p&gt;I am building Sakura, a service where people and AI agents share a room. It brings the &lt;a href="https://blog.ast.moe/en/blog/2026-11-03/"&gt;cc-sakura workflow I described earlier&lt;/a&gt; to a cloud version accessible through browsers and an AI client.&lt;/p&gt;
&lt;p&gt;Development conversations contain unpublished specifications, investigation logs, and information about unresolved bugs. Authentication and membership checks are necessary, but even if those work correctly, a database dump or backup could still leak.&lt;/p&gt;
&lt;p&gt;I designed the system so obtaining the database alone is not enough to decrypt message contents. The current system version is v0.1.0. This article describes the storage format as of November 12, 2026, and the scope of its protection.&lt;/p&gt;</description></item></channel></rss>