An easy way to change the master password, settings and thus all generated passwords: PasswordMaker remembers old settings.
Situation:
A user wants to change his master password (or any other setting), maybe regularly, maybe only once because of a security risk. Maybe he wants to change the character set because one site doesn't like the special characters. He wants to change all his passwords on all his sites.
He has used PasswordMaker on many sites, some of which he uses rugularly, some only seldomly.
Problem:
He has to change the password on all these sites to the new generated password, and he has to remember on which sites the already changed, and which ones still use the old password. He has to retrieve the old passwords from PasswordMaker, change settings back and forth, or create accounts for this, or use other means. He doesn't want to spend the time to go through all his sites at once, he wants to change them when he visits the site the next time. He would like to have an easy way to change the password on these sites.
Solution:
A new function in PasswordMaker named Archive (or something else), which stores the complete settings and - if it has been changed - the old master password which is ENCIPHERED with the new master password. So the archive is useless without the (new) master password.
In practice:
After archiving the settings with the new password and using it as his new master password, he wants to do a log in at some site, and the new generated password (via CoolKey) doesn't work (of course).
POSSIBLE IMPLEMENTATION:
If CoolKey is activated for a second time within a time frame, it fills the password field with the password generated with the archived settings. And only the first password field, if there's more than one on that page.
On the log-in form the user double clicks on the CoolKey (he hits it twice within a time frame). So on the second click CoolKey replaces the new password with the old one.
Now the user navigates to the page on which to change his password, and again clicks CoolKey two times. On the first click all password fields are filled with the new generated password (behaviour like now), on the second click the first field is filled with the old password. The user hits enter, and his password is changed.
Possible variations:
The archive can store more than one entry, and to retrieve the older settings, you hit CoolKey three times, etc, or use a dropdown menu/context menu.
Some people might want to change their passwords regularly, like every month, and use the modifier field. The archive function can retrieve the password that was generated with an earlier modifier.
The archive function can be used for a single account or a single group. (If only settings are changed, and not the master password.)
PasswordMaker can keep a list of sites where the password has been changed, and act accordingly. (Not useful for people who use more than one computer and don't want to synchronize every day.)
The could be visual feedback as to which password is filled in (maybe changing the color of the key, or displaying a tiny number next to the key on the task bar, or a text in the status bar).
Add your own variations here...
