client side authentication illustrated 🤦🏼♂️
Image transcripion: shows a red sign with white text that says "STRICTLY NO ACCESS" mounted on a metal gate. The gate appears to be part of a fence around a park, with trees visible in the background but there is no fence around the gate or anywhere else
(Originally published earlier today on mastodon.social)
157
Comments13
I generally use this picture to explain client-side security to an unsuspecting audience
Image transcription: A public emergency telephone with a sign stating "Only 911 can be dialed," with the numbers 9 and 1 buttons taped to make it the only accessible dialing option.
Joke's on them. The number I wanted to dial was 1-999-999-9999.
Whose that number?
https://imgur.com/EnFH460?r
There’s a difference between ‘I would rather the user didn’t do that’ and ‘We must not allow this to happen’.
User enters the empty string for their password recovery question? Don’t care. Let the Frontend handle this. If the user is capable enough to disable the frontend validation, they’re capable to remember their password.
User enters SQL as their password recovery question? Validate in the backend.
The issue with your example is that it could be that there was a bug and the user didn’t disable the validation and intend to send an empty string.
The key-code to open the gate is: 1234
they mean for wheelchairs.
window.isAuthenicated = true;
It’s a suggestion, and just enough enforcement to stop people from accidentally wandering that way. Who knows, it might actually be a “don’t go this way, there’s something dangerous” kind of thing, or they could have actual security further along.
When will Linux introduce the feature of a changeable name of the superuser? I don't like the name root, I want to change it on my system. Proper flexibility allows greater security as well as more fun for the user.
To be fair, I’d give up. Don’t want to get muddy shoes. Take the hint I say.
- in actuality the gate would be half that height.