Re:Password may not contain: select, insert, update, delete,...
by roughly on Sunday January 21, 2024 @06:36PM
(#39084197)
Yes! Firesheep was the extension, and I think the combination of that and LetsEncrypt (which was in part a reaction to Firesheep) were the reason the web went from almost entirely decrypted by default to almost entirely encrypted by default in a matter of months. The capabilities had been there for years, but Firesheep made session hijacking a literal one-click affair and vividly highlighted the danger of unencrypted web traffic - it’s maybe the most impactful bit of white-hat hackery of all time.
Re:Password may not contain: select, insert, update, delete,...
by nijave on Sunday January 21, 2024 @08:07PM
(#39084862)
Iirc Google said they'd start penalizing non https sites in search results and browser makers added much more aggressive warnings to http pages.
It caused quite a commotion among small site operators.
Re:Password may not contain: select, insert, update, delete,...
by nicolas_t on Sunday January 21, 2024 @11:05PM
(#39086066)
I remember back in that time that a lot of apps had convoluted code to do this https only at login dance. All in the name of performance (because https was slower despite it being a premature optimization really).
Switching to https only actually mostly helped simplify codebases...
Re:Password may not contain: select, insert, update, delete,...
by singingfish on Monday January 22, 2024 @02:48AM
(#39087312)
yeah, a colleague and I ripped out all of the http / https dance out of a 20 year old code base a little while back. It simplified things a lot.
It’s insane how long it took to see widespread HTTPS adoption.