That said - do you have any really convincing argument as to why having this value be in an editable form would provide any *real* added value? Flexibility for flexibility's sake is not necessarily a 'good thing' - and in fact can create more room for user error/confusion, which I think this would do. As long as it provides the ability to have a unique value for each domain/pattern/entry, it provides the functionality you want (different password for each URL), with no added room for user error.
Ultimately, though, you could make a FR for this to be added to the 'Advanced Security Mode' (which will be the current 'URL Pattern' manager) as an editable field, but I don't know if Eric will be interested in implementing it or not.
I think my examples above showed how the flexibility would be important, at least for me. One ofmy main issues revolves around managing 10+ websites, each has different services: blogs, databases, wikis, admin consoles, ssh, ftp, secure directories, .... So, for example, I would like to create patterns to match the specific parts of the URLs for each of these services and use different components to ensure the passwords don't strictly rely on the same string, and hence produce the same password, for each service. As it stands, I have dozens of accounts, one for each service, with lots and lots of duplication and minor changes to REs and URLs used for password generation.
One example of a benefit to combining many accounts under a single password model is if I chose to change something about these passwords, for example, change the length, I can duplicate one account, make the change and have both accounts available for logging in using the old account, then using the new account for changing the password. As it stands, I generally have at least three, sometimes as many as five or six, PWM accounts to duplicate per "account" if I need to change something about the passwords. So really, I want as few PWM accounts as possible when I'm dealing with accounts in which I only care about the password model. Versatility in the value used to generate passwords is important for this.
