I had the idea of converting map locations into passwords. Basically Jumblar (github.com/micheal-swiggs/jumblar) takes a hash of the user's location and stores this as a comment on the PGP network. The 'stored-hash'(Vague-Hash) currently is only 2-bytes long. Each time the user wishes to use that location to generate passwords, they will first attempt supply a guess location. Jumblar then spirals around this guess location until it finds the point with the same hash.
Jumblar then uses this location as the basis for password generation. The user will add a 'spice' e.g email@example.com that Jumblar will use to generate a password. So rather than the user remembering a map location for each password, they only need to remember one location and a list of spices. Currently I'm assuming that is fine to store the spice(s) in open storage. So long as the map location remains a secret, the passwords derived from the spice(s) are 'safe'.
When Jumblar (github.com/micheal-swiggs/jumblar) generates a password there is a guarantee that it will contain atleast - one lowercase, one uppercase and one numeric - character.
Jumblar only does a vague-hash of the secret location. Rather than storing the entire location hash on the PGP network, Jumblar only stores between 2-3 bytes of hash material. So a potential cracker could only discover a set of possible points that correspond to the vague-hash. The vague-hash is only used to distinguish the secret location from immediately surrounding locations. If the user guesses a location far away from the actual location, then Jumblar is likely to match an incorrect location.
A review and/or comments of the 'idea' and even the project would be greatly appreciated.
Salt & Master Password
The user must also remember a 'master' password and a salt accompanies each vague-hash. So the vague-hash is a result of hashing upon the secret location, password and salt.