You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I wonder if additional charsets could be added, that would exclude visually similar characters, e.g. O vs. 0 or l vs. I vs. 1.
Additionally, letters Z and Y are swapped in many european countries, so we tend to not include Z, z, Y, and y in password charsets.
The easiest and most universal solution would probably be to add a user-defined custom charset that would be read from a configuration file during app init.
The text was updated successfully, but these errors were encountered:
That's a central European thing. In Germany for example, many developers have both DE/DE keyboard layout (QWERTZ) and EN/US keyboard layout (QWERTY) configured on their computers and switch between them regularly. They then tend to type Z instead of Y and vice versa and not notice such mistakes in masked password fields (***********), which then sometimes leads to account lockouts. IT workers in Germany, Austria, Poland, Switzerland, Czechia, Slovakia, Croatia, or Hungary thus prefer having passwords that do not contain letters Y and Z.
As I was saying, it is impossible to satisfy all users with predefined character sets, so a user-defined custom charset would be a great feature.
Hello, I wonder if additional charsets could be added, that would exclude visually similar characters, e.g.
O
vs.0
orl
vs.I
vs.1
.Additionally, letters
Z
andY
are swapped in many european countries, so we tend to not includeZ
,z
,Y
, andy
in password charsets.The easiest and most universal solution would probably be to add a user-defined custom charset that would be read from a configuration file during app init.
The text was updated successfully, but these errors were encountered: