ability to not use some characters
different sites have different requirements re: characters. for a recent password, I had to increase the counter to 6 before I finally found a password that worked. It would be great if I could tell the generator never to use ")" for example.
Dominik
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Uppis on 06 Jun, 2016 07:15 AM
Yes, I also think, that e.g. the "Long" category would otherwise be most useful, except that the templates are quite limited !? In my company for instance the requirement for 12 char passwords is that there should be 2 numbers.
Why spare characters in the first place? In my opinion most used character class in those templates should be 'x'or at least 'a' !?
Support Staff 2 Posted by Maarten Billemo... on 07 Jun, 2016 02:18 PM
These are vaguely valid requests but implementing them would break a key part of the MP solution, which is that it must be stateless. Any custom or complicated site-specific templating would render the password more and more stateful.
There is no way to cover ALL cases here. Password policies are spawn of hell and they should be abolished. Especially retarded ones like "two numbers" or "no )". Please petition the relevant IT department to fix these insane and nonsensical policies. There is absolutely no beneficial justification for these types of rules.
As for, why does Long use letters and not x type characters, the reason is that the intention behind the Long template is to generate a password that is both extremely high in entropy as well as always being legible and fairly memorable.
That said, there is an improvement https://project.lyndir.com/youtrack/issue/MP-8 where we can discuss these things further and try to find a good solution.
Maarten Billemont closed this discussion on 07 Jun, 2016 02:18 PM.