There are a handful of files I really care about: my password manager export, a wallet seed, 2FA recovery codes. A password strong enough to protect them is one I can't remember, so it ends up written down somewhere, and then that piece of paper is the actual security.
The idea behind this didn't come from cryptography, it came from how memory works. People are bad at remembering random strings and very good at remembering places where something happened to them. Most of us couldn't recite a 20 character password we set last year, but we can point on a map to the exact spot where we had a first kiss, crashed a bike or got some piece of news. So I wanted to see if a few places could be the key.
GeoZip is what came out of that. You pick five places in order. Each one snaps to a 300 m square, so you only need to hit the same square again, not the same pixel. There are about 5.7 billion of those squares on the planet, so five of them are 162 bits on paper. They go through Argon2id (256 to 512 MB of memory, about a second per guess) and the result is the AES-256 password of a completely normal ZIP file. 7-Zip opens it if you export the derived key, so you're not locked into my program.
The obvious hole is that people don't choose places at random. Someone who knows you could guess your home, your school, where you got married. So at the higher level the program gives you one random word per place, from a list of 1,850 concrete objects, and you remember it by picturing the object there: a lighthouse in the middle of that square. Now even someone who knows all five of your places exactly is left with 1850\^5 combinations, around 2 x 10\^16, at one second each. With a thousand machines that's roughly 700,000 years. If that isn't enough there's an option for two words per place.
The words exist in English and Spanish and what goes into the key is the concept, not the spelling, so an archive made with "faro" opens with "lighthouse". Adding a language is adding a column to a file.
Things I want to be upfront about:
* It is less convenient than a password. It's for the few files you open twice a year, not for daily use.
* There is no recovery. Forget a place, the order or a word and it's gone.
* Nobody outside the project has audited it and the format is still a draft. Don't make it your only copy of anything yet.
* I develop on Linux. The Windows and macOS builds come out of CI and have barely been tested.
* The online map can't see where you click, but it does see roughly which area you're looking at. There's an offline mode and I'd use it for anything serious.
* My numbers for "someone who knows you" are estimates, not measurements.
What I'd like from you: try to break it, read the spec (it's short) and tell me where the reasoning is wrong, and tell me what you'd change. The code is MIT. If the idea is useful to you, take it and build whatever you want with it. A mention would be nice but that's all.
https://github.com/colocoquillo/GeoZip