3 ms·
So, basically we've just recreated http://supergenpass.com/ http://supergenpass.com/ which has been around for at least a decade. And I'm sure the idea is older
by eli 16y ago
So, basically we've just recreated http://supergenpass.com/ http://supergenpass.com/ which has been around for at least a decade. And I'm sure the idea is older than that.
What happens when the generated password doesn't meet the strength requirements for the site (too long/too short, not enough/too many numbers, not enough "special characters")? Or when I'm required to change my password periodically?
- tzs 16y agoThe way I was going to handle that when I designed my own password generator to replace my encrypted text file of passwords was to store a version number of each site. The version number would be part of the input to the hash. Changing the password for a site then would just require changing the version number. Requirements and restrictions on the password content could be handled similarly, by storing password formatting information for each site. I never got around to implementing my system, because I got a fantastic deal on 1Password (via MacHeist) and my system became completely pointless.
- cpeterso 16y agoSuperGenPass has a serious DOM vulnerability. The link has a live demo. http://akibjorklund.com/2009/supergenpass-is-not-that-secure http://akibjorklund.com/2009/supergenpass-is-not-that-secure The SuperGenPass UI is rendered within the DOM of the current page when you click the bookmarklet. The UI is where you enter your master password. And because the UI is part of the current page, any script running in the page can read your master password. Remember that script can be external too, as in advertisements or widgets of some kind.