Image description: 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 on mastodon.social: 2024-02-18)
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.
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.
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.
How about input sanitization entirely on the client side? That's what a university did with its exam results database. I wonder how many times it got hacked.
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.