3 ms·
Right, but it was pushed as "lock icon means secure" and end users don't distinguish threat models.
by yjftsjthsd-h 8y ago
Right, but it was pushed as "lock icon means secure" and end users don't distinguish threat models.
- ldng 8y agoExactly, and I disagree on education. People can and must be taught on security (not just phishing). But that also mean some standardization on the browser UI and not trying to make it "seamless" and "transparent". This exploit is the result of voluntarily blurring the lines between Traditional Apps and Web Apps. Well, the threat model being very different, it's not a good idea. HTTPS is a part of a whole and pushing so hard make people (even tech savvy ones) focus too much on it. How many CTOs are happy with just putting HTTPS on their website so they can check the security checkbox ?
- WorldMaker 8y agoWhich is arguably why the push is increasingly to "Not Secure" and "Is Maybe Secure" notifications over "Is Secure". Maybe that will help more end users.
- dcbadacd 8y agoPast malpractice shouldn't be the reason for no future improvement. It's simply the time to relearn.