CipherStash founder, cryptography nerd, Rust zealot.
Sydney and SF
Joined May 2008
- Tweets6.5K
- Following4.8K
- Followers7.9K
- Likes6.8K
What an epic event! @supabase select was so much fun.
Still so honoured to be partnered with this incredible company.
Anthropic just used Claude to break RSA-896 encryption.
It was only 16-days after RSA-260 was broken and RSA-1024 is the next target.
Should we be concerned?
No. In fact, I think it’s a good thing.
The breakthrough here was to use GPUs instead of CPUs to find prime factors in parallel. Reducing the time to just 10 days instead of literally decades.
Claude didn’t find a new algorithm - it wrote the code to make GNFS (General Number Field Sieves) work in parallel. Seriously impressive but not for the reason that headlines will have you believe.
RSA-896 is old and hasn’t been a standard since 2007.
If you still use RSA, you likely use 2048 or 4096-bit keys.
Are they at risk?
At face value, it seems like it’s just a matter of time before RSA of any size will be easily factored. But the jump from 1024 to 2048 is astronomical compared to the one from 260 to 896.
Assuming the GPU approach scales, factoring RSA-2048 would take ~510 million years on the same 2048 GPUs used to break RSA-896. RSA-4096 would take 430 quintillion years - or 31 billion times the current age of the universe!
Larger RSA keys are perfectly safe from this kind of attack (though the jury is still out on the practicality of quantum attacks any time soon).
So, why do I think this is a good thing?
It reminds us that most cryptography is about computational advantage. And AI driven results like this push technology providers to ensure they use the current best practices.
There’s no hiding anymore - if there’s a weakness, AI will find it, forcing the adoption of better tech. And that’s a good thing!
Mutant tooling is available for most languages. Check out Stryker (JS, Scala, C#), Mutmut (Python) or Gremlins (Go). Leave a comment if you know of others!
Mutation testing is one tool in the kit. Follow me for more.
Dan Draper retweeted
Prisma 8 just hit release candidate.
And it has searchable encryption built in thanks to CipherStash.
We’ve worked with the Prisma team to give you:
🔎 Encrypted search
🔽 Encrypted Sorting and range queries
📃 Searchable encrypted JSON
All natively in Prisma 8’s shiny new API:
✅ Prisma migrations support encrypted data
✅ Prisma schema works with encrypted data types
✅ Prisma queries work with encrypted queries
Plus, its fully supported in Prisma Compute and Prisma Postgres.
Data Level Access Control just got even easier. Full announcement in the comments.
Dan Draper retweeted
Today we're launching the CipherStash + Supabase integration.
Developers can now build privacy-first PostgreSQL applications without giving up the features they expect.
What you get:
* Search encrypted data (equality, range, ordering & full-text)
* Encrypt sensitive fields before they ever reach Postgres
* Keep keys under your control with ZeroKMS
* Add data-level access control tied to identity
* Works natively with Supabase and TypeScript
This is about making strong security the default—not something that slows developers down.
Learn more:
cipherstash.com/supabase
Docs:
cipherstash.com/docs/integra…
Thanks to the @supabase team for partnering with us. Looking forward to seeing what everyone builds next.
This is the one I've been waiting to share.
Searchable encryption on @supabase is live! Encrypt your columns and keep querying them. WHERE, LIKE, ORDER BY, JOIN, GROUP BY, even JSON. Basically, zero code change and < 10ms overhead for most queries.
CipherStash brings searchable field-level encryption to Supabase.
→ Encrypt sensitive fields at the application layer, no schema changes
→ Search, sort, and join over encrypted data without decrypting it
→ Keys stay under your control with ZeroKMS
One command to set up: `npx stash init --supabase`
Learn more → supabase.com/blog/searchable…
I pointed Claude Fable at a major update of one of our crypto libs over night. It more than quadrupled encrypt performance and found an obscure encrypt-side timing security flaw that exists in our scheme as well as all of the current published ORE schemes in the literature. Mind blown.
...and now Fable has been disabled.
I love this! Great move from the @prisma team
Most Postgres hardening guides are checklists in no particular order.
Attackers don't probe in no particular order.
Here's how to secure a Postgres database in the sequence an attacker would actually work through it 🧵
The fix: encrypt in the application, so Postgres never holds plaintext or key material.
The catch was always search. WHERE email = ? dies on random ciphertext. Encrypted indexes solve it: the planner uses them like any other index.
A pg_dump shows ciphertext. Nothing else.
Doors five and six: backups (a complete copy of your database with none of its access controls) and unapplied patches (a door you know is open, and so does everyone else).
Work through the doors in order. The attacker will.
Runnable commands for all six: dev.to/cipherstash/securing-…
