417

submitted 1 week ago* (last edited 6 days ago) by qaz@lemmy.world to c/programmer_humor@programming.dev

68 comments fedilink hide all child comments

...

you are viewing a single comment's thread
view the rest of the comments

[-] sus@programming.dev 13 points 1 week ago* (last edited 1 week ago)

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

[-] planish@sh.itjust.works 5 points 6 days ago

If the password is going in URLs you already have a problem.

[-] Quibblekrust@thelemmy.club 1 points 3 days ago

It's safe for https.

[-] planish@sh.itjust.works 1 points 2 days ago

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.