News for hackers. Stuff that matters.
Re:Preventing CSRF with the same-site cookie attribute by jerf on Saturday April 16, 2016 @08:21PM (#11512929)
I think a great deal of the problem is more that the new security standards don't work for any existing sites (to speak of). Retrofitting these things on to existing sites is more work than most people are willing to take on. (I am aware of some exceptions, but many of those exceptions got there only via paying out on quite a few bug bounties first.) They're really only useful for new sites. Some of them are only useful for new sites that are security-conscious, too... my bank's web access portal touches only three domains, all owned by the bank. (Although I'm suspicious about the check-ordering component, which I didn't count in that 3.) They going to have an easier time implementing this sort of feature than someone trying to bring in twelve different advertisers and trackers and dicking around with iframes and whoknowswhat.

But if you never put them in the browsers because "nobody" can use them, it is a certainty that nobody ever will.

Personally, I can't say as I mind some security features that will discourage splaying web sites across dozens of unrelated domains....

There are no comments on this comment yet.