News for hackers. Stuff that matters.
Re:A proposal to restrict sites from accessing a users' loca... by formerly_proven on Thursday June 05, 2025 @07:10AM (#44190458)
That highly ranked comments on HN (an audience with way above average-engineer interest in software and security) get this wrong kinda explains why these things keep being an issue.
Re:A proposal to restrict sites from accessing a users' loca... by lyu07282 on Thursday June 05, 2025 @11:06AM (#44192409)
I don't know why you are getting downvoted, you do have a point. Some of the comments appear knowing what CORS headers are, but neither their purpose nor how it relates to CSRF it seems, which is worrying. It's not meant as disparaging. My university thought a course on OWASP thankfully, otherwise I'll probably also be oblivious.
Re:A proposal to restrict sites from accessing a users' loca... by asmor on Thursday June 05, 2025 @06:04PM (#44196203)
If you're going cross-domain with XHR, I'd hope you're mostly sending json request bodies and not forms.

Though to be fair, a lot of web frameworks have methods to bind named inputs that allow either.

Re:A proposal to restrict sites from accessing a users' loca... by bawolff on Friday June 06, 2025 @03:20AM (#44198552)
This misses the point a bit. CSRF usually applies to people who want only same domain requests and dont realize that cross domain is an option for the attacker.

In the modern web its much less of an issue due to samesite cookies being default .

Re:A proposal to restrict sites from accessing a users' loca... by mrguyorama on Friday June 06, 2025 @02:41PM (#44203753)
I'm betting HN is vastly more normal people and manager types than people want to admit.

None of us had to pass a security test to post here. There's no filter. That makes it pretty likely that HN's community is exactly as shitty as the rest of the internet's.

People need to stop treating this community like some club of enlightened elites. It's hilariously sad and self-congratulatory.