<?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>Encryption on Momo Engineering Journal</title><link>/tags/encryption/</link><description>Recent content in Encryption on Momo Engineering Journal</description><image><title>Momo Engineering Journal</title><url>/images/og-image.png</url><link>/images/og-image.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 11:26:56 -0600</lastBuildDate><atom:link href="/tags/encryption/index.xml" rel="self" type="application/rss+xml"/><item><title>Rotating Secrets Without a Secret Server: Deriving, Versioning, and Hot-Reloading Keys</title><link>/posts/054-secrets-management-key-rotation/</link><pubDate>Tue, 25 Aug 2026 03:25:35 +0000</pubDate><guid>/posts/054-secrets-management-key-rotation/</guid><description>How momo manages encryption keys without a central secret server: a pluggable provider chain (env, then config file), a per-node versioned key registry in local storage, and rotation that promotes a new key without any downtime. Teaches: why a provider chain beats a single source, how key versioning enables online rotation, and when rotation is and is not worth the complexity.</description></item><item><title>Tenant Isolation: Deriving Per-Tenant Keys, Enforcing ACLs, and Proving What Happened</title><link>/posts/053-multitenancy-authorization-audit/</link><pubDate>Tue, 25 Aug 2026 03:25:29 +0000</pubDate><guid>/posts/053-multitenancy-authorization-audit/</guid><description>How momo isolates tenants without a central secret server: HKDF-derived per-tenant keys, default-deny ACLs evaluated per request, and a SHA-256 hash-chained audit log that makes tampering detectable. Teaches: key derivation vs. key storage, why ACL evaluation order matters, and how hash chaining turns a log into evidence.</description></item><item><title>Client-Held E2EE: Envelope Encryption Real</title><link>/posts/013-e2ee-envelope-encryption/</link><pubDate>Tue, 11 Aug 2026 16:36:53 +0000</pubDate><guid>/posts/013-e2ee-envelope-encryption/</guid><description>Envelope encryption with a client-held key: the server stores ciphertext and can&amp;rsquo;t read it — across S3 and native transports.</description></item></channel></rss>