4 ms·

He forgot to mention hiding sensitive information behind a JS-powered script that had the password saved in the clear in the script on the page, and then disabl

He forgot to mention hiding sensitive information behind a JS-powered script that had the password saved in the clear in the script on the page, and then disabling right-click events so you couldn't inspect the source of the page to find the super secret password... Hint: it was totally unsafe then, it still is now.

progre 5y ago
I, as an embedded developer working for a vending machine manufacturer did this about 10 years ago. The sales people came running and asked me to help them "fix the home page" because the sales chief had realised that diffrent markets could see what prices the other markets was being charged. Not being a web guy, I said that we probably should have a look at the server code to see if we could figure out what to do. Turns out there was no server code, just static web pages. I said we could probably password protect the price lists with javascript but any child who knew how to hit F12 would be able to see the prices anyway. They said "What's F12? Can you do it today?"