maybe they were looking for extra special characters like 🁄 or ⶸ. Who am I kidding, RFC 1738 tells us that literally everything is unsafe and you know, we need to prepare for the inevitable occasion when the password somehow ends up inside an URL.
The characters “<” and “>” are unsafe because they are used as the delimiters around URLs in free text;
the quote mark (“”") is used to delimit URLs in some systems.
The character “#” is unsafe
The character “%” is unsafe
It ends up with
Thus, only alphanumerics, the special characters
$ - _ . + ! * ’ ( ) ,
are safe
and when the rule is also wrong example: password must contain special charcters
the password in question contained : and ^
if those aren’t special characters idk what is
I never get bored of discovering yet another software that gets broken because someome put a dollar sign in their password…
Often only a few special characters are accepted. Punctuation yes, emoji no.
“Punctuation yes, emoji no” sounds like something a grade school teacher would have embroidered on a throw pillow.
maybe they were looking for extra special characters like 🁄 or ⶸ. Who am I kidding, RFC 1738 tells us that literally everything is unsafe and you know, we need to prepare for the inevitable occasion when the password somehow ends up inside an URL.
It ends up with
If the password is going in URLs you already have a problem.
I am going put null on my password and you aren’t stopping me