I hate when websites have some weird rules for passwords, and show the rule when you are creating the password, but not when entering it. How am I supposed to remember the password must begin and end with a special character?
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
But if you put the password in a URL, the user’s browser is going to turn around and store that plaintext password in its history, then sync it to the user’s other devices, and then pop it up on their screen in the address bar autocomplete, perhaps when the user is screen sharing or streaming to hundreds of people. The browser does not expect a password to be stored there and will mishandle it.
Having to alter my one generic password I use for random ass website because there’s a stupid extra rule is usually annoying me enough that I don’t register lmao.
In that case consider your accounts on “everything else” to be compromised already. It can be a pretty significant vector for identity theft for example.
honestly I prefer to go the other route : if a website complains about a generic randomly generated password , especially if they have very specific rules I take it as a challenge to make a password with as much entropy as possible , preferably to the point where any reasonable hash can express less entropy
I hate when websites have some weird rules for passwords, and show the rule when you are creating the password, but not when entering it. How am I supposed to remember the password must begin and end with a special character?
I can’t recommend password managers enough, because you will never have this issue again.
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
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.
It’s safe for https.
In terms of the transport, sure.
But if you put the password in a URL, the user’s browser is going to turn around and store that plaintext password in its history, then sync it to the user’s other devices, and then pop it up on their screen in the address bar autocomplete, perhaps when the user is screen sharing or streaming to hundreds of people. The browser does not expect a password to be stored there and will mishandle it.
Nah, if you type a password in a url, it gets turned into asterisks. Look: https://google.com/?password********************
I am going put null on my password and you aren’t stopping me
Also [object Object] is always a classic to mess with any js
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.
Having to alter my one generic password I use for random ass website because there’s a stupid extra rule is usually annoying me enough that I don’t register lmao.
Password manager?
I use it for important things that require actual security. Everything else gets the one password treatment.
In that case consider your accounts on “everything else” to be compromised already. It can be a pretty significant vector for identity theft for example.
I’m not dumb enough to share important private information on websites that don’t require it.
I use a mental algorithm that means my password is always different on paper, but is always deducible by me.
honestly I prefer to go the other route : if a website complains about a generic randomly generated password , especially if they have very specific rules I take it as a challenge to make a password with as much entropy as possible , preferably to the point where any reasonable hash can express less entropy