|
|
|
|
|
|
by JulianMorrison
3511 days ago
|
|
|
In principle you could add a post-generation step that takes a description of the site's particular brand of password limitation damnfoolery and munges the output to fit. Then this profile would need to be saved somewhere so the same step could be done at password filling time. (Still less sensible than doing this once and encrypting the result.) |
|
|