Most simply, I'm trying to create an account that acts similar to the default account. That is, one that uses the current URL as the URL for calculating the generated password. Currently, there seems to be no account other than the default that can use the current URL for generating the password. All the accounts I create have to use a fixed string for the string used for generating the password.
To see what I mean, edit an account and click on the URLs tab. The top input box is the issue. It should allow me to specify elements from the matched patterns I specified for that account (the patterns which are also specified on the URLs tab).
For example, I have lots of accounts where the only difference is the URL. It'd be much easier to manage if I could have just one account that could generate the password for them all. This is basically what the default account is for but I need different "default settings" for different situations. For example, some passwords are longer, some exclude certain characters, use different algorithms, ...
Basically, one way to look at what I'm asking for, is the ability to collapse accounts into a single account and specify a bunch of patterns for each of the hosts and the matched host is used for generating the password. Note: I'm really asking for something far more general but that's one way to understand what I want.
e.g. One account might be where the sites allow 20 character passwords
The URL to use for generating password: $2 (note: this refers to the second RE grouping of the matched patterns below, like how perl handles RE matches)
Patterns:
^[^:]//([^.]+[.])?(yahoo[.]com)[:/].*
^[^:]//([^.]+[.])?(google[.]com)[:/].*
^[^:]//([^.]+[.])?(flickr[.]com)[:/].*
^[^:]//([^.]+[.])?(myspace[.]com)[:/].*
^[^:]//([^.]+[.])?(claimid[.]com)[:/].*
then another account for sites that limit passwords to 8 characters and only letters and numbers:
The URL to use for generating password: $2
Patterns:
^[^:]//([^.]+[.])?(aninsecuresite[.]com)[:/].*
^[^:]//([^.]+[.])?(nothingimportant[.]com)[:/].*
^[^:]//([^.]+[.])?(constantlycracked[.]com)[:/].*
^[^:]//([^.]+[.])?(brokendaily[.]com)[:/].*
^[^:]//([^.]+[.])?(microsoft[.]com)[:/].*
One additional feature might be to generalize this into how the default account works in this respect, that is, on the URLs tab, the "URL Components" check boxes. Though, these user-defined accounts must still support pattern matching unlike the default account. In fact, it would be really nice if the patterns were even generalized into the URL components. Notice how my patterns always follow the same format. The patterns should be broken into input boxes for [protocol][subdomain][domain][TLD][port][path][query] so that passwordmaker and ensure secure patterns for any element not specified.
