"Special" password character set is non-extensive and, worst of all, opaque for the user.
mtMp`2mhbtytvsN?)`Zf(W/]
Should contain at least one special character error and a major confusion
Successful creation of account or at least error message stating which characters stack expects to be present in the password as "special".
Any
Either the "special" password character set should be extended, or the "special" character set should be defined clearly, such that users know, which characters we consider "special".
yes
As I commented on Slack yesterday:
Let's redefine that "special char" category to:
09 and AZ and az
- Any char smaller than
0
If we start doing numeric char comparison, then I'd suggest "Any char between (space) and 0.
Chars under 0x20 are non-printable and space itself is quite confusing as a "special char", but we could allow it as such.
Most helpful comment
As I commented on Slack yesterday:
Let's redefine that "special char" category to:
09andAZandaz