Dshamir quietly bolsters the plumbing - and lets stored keys rotate without downtime
Three small backend additions, but the one that matters lets the team swap the encryption protecting users' stored API keys without ever taking the service offline.
Dshamir's fork adds a trio of behind-the-scenes building blocks. Two are about speed: a caching layer (built on Redis, an in-memory data store that keeps frequently used results close at hand) and standard controls that tell browsers and proxies how long they can safely reuse a response. Useful, but invisible to most users.
The third is the one worth noting. The fork can now rotate the secret key that encrypts users' stored credentials - re-encrypting everything under a fresh key while the service keeps running. It does this by trying each configured key in turn, so old and new can coexist during the changeover. For anyone storing sensitive third-party credentials inside a legal-AI tool, the ability to retire a compromised or aging key without an outage is the difference between a routine security hygiene step and a painful migration.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?