News for hackers. Stuff that matters.

A comment on It’s time to kill the web app. Parent comment

Re:It’s time to kill the web app by Pxtl on Saturday September 23, 2017 @06:09PM (#15322046)
Yes, but then the malware can also compromise the server, since it now has js access to all the users and can Masquerade as them when they see the ad - even as admins. Keys to the kingdom. This is a feature, not a bug - it means the user and the server are now in the same boat, and the server will have some friggin diligence about whose code they run.

Also, means the server has to pay for the damned bandwidth.

[ Parent | on HN ]
Re:It’s time to kill the web app by NMDaniel on Saturday September 23, 2017 @07:21PM (#15322316)
That's not how it works, the server wouldn't execute JS that is meant for a browser client, it would just serve it like any other static file.

What you're suggesting will actually hamper security, because scripts served from your domain have less limitations(see https://en.wikipedia.org/wiki/Same-origin_policy , https://en.wikipedia.org/wiki/Content_Security_Policy and other mechanisms)

[ Parent | on HN ]
Re:It’s time to kill the web app by leeoniya on Saturday September 23, 2017 @07:28PM (#15322348)
the implication of same-origin would affect all requests made from the client. you can serve malicious js from the server all day long but it would be restricted to only talking back to that same server.
[ Parent | on HN ]