5 ms·
Here's my crazy crackpot theory for solving the password problem. Users should have a handful of passwords, in the old security-level style; everyday sites use
by barrkel 14y ago
Here's my crazy crackpot theory for solving the password problem.
Users should have a handful of passwords, in the old security-level style; everyday sites use a short simple password, email a level up, banking a level up again.
But the passwords should not be entered directly into sites. Instead, they should be hashed by a browser feature / plugin, roughly equivalent to bcrypt(password + user-specific-salt + site DNS name). The output of this process is what gets provided to sites. Not all sites will accept the full entropy of bcrypt or similar, so there needs to be a central registry tracking acceptable mappings from the output of bcrypt to the input of a site's password. There's also an issue around sites that share accounts across different top-level DNS names - Amazon in particular - that can also be handled by the same central registry technique.
This way, there is no list of passwords to worry about backing up, losing or handing over to third parties - everyone should be able to remember two or three passwords. There is no Javascript vulnerability like you see with bookmarklets for things like SuperGenPass. Every website sees a unique and specific password, even if the same underlying password is used by different people.
The only thing you need to worry about is your browser getting completely owned, so that the memory space of its extension mechanism is accessed by remote websites. But if the attacker has that level of control, it's not unreasonable to think he has control over a third party password manager too.
What it doesn't do well is revocation and renewal of a password. It also has a single point of failure - if someone somehow gets access to your underlying password, and knows the mechanism and salt, they can open a whole lot of boxes. This, of course, is why I'm a crackpot: I can live with that.
- rapind 14y agohttp://passwordmaker.org/ http://passwordmaker.org/ But you still need to realize that this won't last forever. You can crack an application's hashing algo (and know what hash or field they're using for the salt) because 50% of its users picked crappy passwords. Then if you're really dedicated you can work on the double hashed passwords, knowing that most people use the domain as the salt for browser-side hashing... Also a pre-hashed password has to be pretty easy to spot in a list once you've cracked the server-hash. Scary stuff...
- uvdiv 14y agoThat looks like they're using unsalted SHA-256 as a password derivation function? And they reimplemented every cryptographic primitive themselves? I'll pass.
- rapind 14y agoNot sure where you got that idea, but the Passwordmaker Pro chrome extension I'm using, let's me specify a different salt (domain of the site is the default), let's me pick the hashing algo, the length of the hash, the modifier, characters to use, etc. You might want to look at it again.
- uvdiv 14y agolet's me pick the hashing algo, All of the choices are hash functions designed to be fast (like SHA-256, the default), which you do not want for password derivation because being fast to compute means easy to brute-force. You can test billions of digests per second with a PC graphics card. let's me specify a different salt (domain of the site is the default) Then every user shares the same salt for a given site, which largely defeats the purpose of salting (to prevent rainbow tables).
- rapind 14y agoYeah the salt default being an issue, is what I said in my initial post. I'm going to go out on a limb and say that doing the following will make you one of the hardest passwords to crack during the event of a weak hashing leak like the linkedin fiasco. 1. Install and use the Passwordmaker Pro extension. https://chrome.google.com/webstore/detail/ocjkdaaapapjpmipmhiadedofjiokogj https://chrome.google.com/webstore/detail/ocjkdaaapapjpmipmh... 2. Change the default password length to say 40 characters. 3. Add a modifier like bOoo7&jd8$02jf 4. Change whatever other defaults you want. 5. Use a master password that's at least 10 characters long. BTW it would be easy enough to fork this extension and provide a little more security if you wanted. https://github.com/bitboxer/chrome-passwordmaker/ https://github.com/bitboxer/chrome-passwordmaker/
- cypherpunks01 14y agoIt's not a crackpot theory, it's awesome - Stanford Password Hash https://www.pwdhash.com/ https://www.pwdhash.com/