<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🔐 SelfDataGuard v0.1.0-beta — open-source data-at-rest protection that survives DB exfiltration.]]></title><description><![CDATA[<p><img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f510.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--closed_lock_with_key" style="height:23px;width:auto;vertical-align:middle" title="🔐" alt="🔐" /> SelfDataGuard v0.1.0-beta — open-source data-at-rest protection that survives DB exfiltration.                                                                                                                 <br />                                                                                                                                                                                                                    <br />  Released today as the second pillar of MySelf, paired with SelfRecover. The same May 2026 ANTS leak (~12M accounts in plaintext) made the case for both: SelfRecover protects authentication, SelfDataGuard       <br />  protects what's stored.                                                                                                                                                                                           <br />                                                                                                                                                                                                                    <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f6e1.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--shield" style="height:23px;width:auto;vertical-align:middle" title="🛡" alt="🛡" /> How it works (one line):                                    <br />  Per-user data master key, never stored in plain. Wrapped twice — once by Argon2id-derived key from password, once by HMAC-SHA256-derived key from a memorized secret (shared with SelfRecover via mathematical<br />  context separation). Personal fields encrypted field-by-field with AES-256-GCM. Dump the DB → encrypted soup.                                                                                                     <br />   <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f3af.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--dart" style="height:23px;width:auto;vertical-align:middle" title="🎯" alt="🎯" /> Three operational modes:                                                                                                                                                                                       <br />                                                                <br />  ▸ Lite (default): server unwraps the master key in memory only during user sessions.                                                                                                                              <br />                                                                <br />  ▸ Hybrid (e-commerce): operational fields admin-readable, sensitive fields zero-knowledge.                                                                                                                        <br />   <br />  ▸ Full (high-assurance): true zero-knowledge, all crypto in browser via WebCrypto.                                                                                                                                <br />                                                                <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f52c.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--microscope" style="height:23px;width:auto;vertical-align:middle" title="🔬" alt="🔬" /> Honest threat model — explicitly out of scope: compromised user endpoint (keyloggers, info-stealers), browser exploits, theoretical cryptanalysis of SHA-256 / AES-256-GCM / Argon2id, weak-password           <br />  bruteforce. The lib enforces password policy at deployment time.<br />                                                                                                                                                                                                                    <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f680.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--rocket" style="height:23px;width:auto;vertical-align:middle" title="🚀" alt="🚀" /> Run the demo locally in 10 seconds:                        <br />  git clone <a href="https://github.com/Pierroons/my-self" rel="nofollow noopener"><span>https://</span><span>github.com/Pierroons/my-self</span><span></span></a><br />  cd my-self/self-security/selfdataguard/demo &amp;&amp; ./run.sh<br />  (needs PHP 8.1+ with sodium + AES-NI capable CPU)                                                                                                                                                                 <br />   <br />  🧪 155 sanity tests, 0 failures. Includes a "DB dump = encrypted soup" end-to-end assertion that greps the SQLite file post-write to verify no plaintext leaks.                                                   <br />                                                                <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f4dc.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--scroll" style="height:23px;width:auto;vertical-align:middle" title="📜" alt="📜" /> GPG-signed tag selfdataguard-v0.1.0-beta, release dated 2026-05-08.                                                                                                                                            <br />                                                                <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f517.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--link" style="height:23px;width:auto;vertical-align:middle" title="🔗" alt="🔗" /> Live demo (no signup, ephemeral data, public reset every night at 04:00 Europe/Paris):                                                                                                                         <br />  <a href="https://dataguard.my-self.fr" rel="nofollow noopener"><span>https://</span><span>dataguard.my-self.fr</span><span></span></a>                                  <br />                                                                                                                                                                                                                    <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f4da.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--books" style="height:23px;width:auto;vertical-align:middle" title="📚" alt="📚" /> Whitepaper EN: <a href="https://github.com/Pierroons/my-self/blob/main/self-security/selfdataguard/docs/whitepaper-en.md" rel="nofollow noopener"><span>https://</span><span>github.com/Pierroons/my-self/b</span><span>lob/main/self-security/selfdataguard/docs/whitepaper-en.md</span></a>                                                                                                <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f4da.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--books" style="height:23px;width:auto;vertical-align:middle" title="📚" alt="📚" /> Whitepaper FR: <a href="https://github.com/Pierroons/my-self/blob/main/self-security/selfdataguard/docs/whitepaper-fr.md" rel="nofollow noopener"><span>https://</span><span>github.com/Pierroons/my-self/b</span><span>lob/main/self-security/selfdataguard/docs/whitepaper-fr.md</span></a><br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f527.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--wrench" style="height:23px;width:auto;vertical-align:middle" title="🔧" alt="🔧" /> Repo: <a href="https://github.com/Pierroons/my-self/tree/main/self-security/selfdataguard" rel="nofollow noopener"><span>https://</span><span>github.com/Pierroons/my-self/t</span><span>ree/main/self-security/selfdataguard</span></a>                                                                                                                               <br />  <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f4e6.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--package" style="height:23px;width:auto;vertical-align:middle" title="📦" alt="📦" /> Release: <a href="https://github.com/Pierroons/my-self/releases/tag/selfdataguard-v0.1.0-beta" rel="nofollow noopener"><span>https://</span><span>github.com/Pierroons/my-self/r</span><span>eleases/tag/selfdataguard-v0.1.0-beta</span></a><br />                                                                                                                                                                                                                    <br />  Companion to SelfRecover (<a href="https://bi-self.my-self.fr/selfrecover/" rel="nofollow noopener"><span>https://</span><span>bi-self.my-self.fr/selfrecover/</span><span></span></a>). Same memorized secret unlocks both, mathematically isolated via HMAC contexts (/recover vs /dataguard). One word, two purposes.               <br />                                                                                                                                                                                                                    <br />  Feedback especially welcome from people who have integrated Bitwarden / 1Password / ProtonMail-style envelope encryption in app-side multi-tenant setups. AGPL-3.0-or-later, no NDA, no commercial agenda —       <br />  community cryptographic review before v1.0.0.                 <br />                                                                                                                                                                                                                    <br />  <a href="https://infosec.exchange/tags/opensource" rel="tag">#<span>opensource</span></a> <a href="https://infosec.exchange/tags/infosec" rel="tag">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/AGPL" rel="tag">#<span>AGPL</span></a> <a href="https://infosec.exchange/tags/privacy" rel="tag">#<span>privacy</span></a> <a href="https://infosec.exchange/tags/selfhosted" rel="tag">#<span>selfhosted</span></a> <a href="https://infosec.exchange/tags/cryptography" rel="tag">#<span>cryptography</span></a> <a href="https://infosec.exchange/tags/encryption" rel="tag">#<span>encryption</span></a> <a href="https://infosec.exchange/tags/zerotrust" rel="tag">#<span>zerotrust</span></a> <a href="https://infosec.exchange/tags/dataprotection" rel="tag">#<span>dataprotection</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/5b7a5009-4b1f-478e-a503-8c8d2821c564/selfdataguard-v0.1.0-beta-open-source-data-at-rest-protection-that-survives-db-exfiltration.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 04:33:42 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/5b7a5009-4b1f-478e-a503-8c8d2821c564.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 08 May 2026 15:38:12 GMT</pubDate><ttl>60</ttl></channel></rss>