News for hackers. Stuff that matters.
Re:Microsoft has joined Khronos, WebGL working group by pjc50 on Tuesday August 12, 2014 @09:30AM (#8167628)
The sandbox is a feature afforded by the underlying OS and CPU architecture

Absolutely not; the sandbox of Javascript apps is entirely within the browser. The CPU architecture may theoretically prevent a userspace app from breaking into ring 0, but that's not the interesting thing; you're trying to prevent random apps from gaining access to all the tasty data in userland.

"Please do not download and run random executables" is a lesson that security people have been trying to get across for a while. Running a native game executable involves trusting it not to be malware. Running a webgl or HTML5 game does not.

(The sandboxing of webgl may be dodgy, which is a weakness here.)

Re:Microsoft has joined Khronos, WebGL working group by ksk on Wednesday August 13, 2014 @09:09AM (#8172675)
>Absolutely not; the sandbox of Javascript apps is entirely within the browser. The CPU architecture may theoretically prevent a userspace app from breaking into ring 0, but that's not the interesting thing; you're trying to prevent random apps from gaining access to all the tasty data in userland.

I don't know why you felt compelled to state a categorical denial when the facts dispute it. Please read up on how security tokens work in Windows, for e.g.

http://msdn.microsoft.com/en-us/library/bb625957.aspx

> Running a native game executable involves trusting it not to be malware. Running a webgl or HTML5 game does not.

There is no difference between those two executions in modern operating systems that implement mandatory access control.