4 ms·
A lot of people hated the decision, but back when Microsoft refused to support WebGL, one of the reasons were that the GPU drivers were awful and exposing them
by nailer 10y ago
A lot of people hated the decision, but back when Microsoft refused to support WebGL, one of the reasons were that the GPU drivers were awful and exposing them to the internet was dangerous.
The proper solution, of course, i for GPU drivers not to suck but it was still a legitimate point and this article seems to validate that.
- stuckagain 10y agoThe post specifically mentions that these things are not vulnerable to attack from WebGL, because you can't reach the APIs in question just by drawing.
- gsnedders 10y agoThe parts now exposed to WebGL are pretty well fuzzed at this point; much of the low-hanging fruit has now been picked.
- modeless 10y agoMicrosoft changed their minds and this article validates that the fears were mostly unfounded. Browsers can do enough validation of their own to mitigate most driver issues.
- Eridrus 10y agoThey were right that it was dangerous, but it became pretty clear that IE was using them to provide cover for not implementing a feature when they changed their mind later. Whereas Chrome implemented a WebGL compiler that reduced the amount of attack surface WebGL could reach and audited a bunch of popular drivers to fix the exposed bits. I think the fact that this blog shows that these vulnerabilities are not reachable from WebGL is a validation of Chrome's approach there, though it clearly shows the issues these drivers present for escaping Chrome's sandbox.
- vvanders 10y agoI think there's probably still a fair bit of attack surface behind glReadPixels() and the like. All it takes in a single backbuffer/texture/surface/etc to not be memzero'd properly and you can start looking at parts of the system's memory. GPUs are both really complex and highly secretive about their implementations. The incentive for GPU vendors is to write fast drivers. Security is pretty far down on the list, esp when it competes directly against performance.
- edmccard 10y ago>fair bit of attack surface behind glReadPixels() and the like... >...you can start looking at parts of the system's memory I thought the whole point of using glReadPixels(), as opposed to just dereferencing a pointer in the system's address space, was that the framebuffer memory it accesses (whether backed by a texture or a surface or whatever) is GPU memory, and not system memory?
- vvanders 10y agoThat's true on split-memory architectures(desktop) but most mobile GPUs(and a couple consoles) use a unified memory model. Also most browsers use the GPU to speed up rendering so you can pick out things from there too potentially.
- louithethrid 10y agoI wonder, do you really have to write zero to all the memorycells? Or can you just stop the refresh cycle in hardware and let squares of memory drain and die in one or two cycles?
- Filligree 10y agoThe latter would take far longer, even if it were reliable. So not really; it'd need hardware support to be reliable, and if chipmakers are willing to do that, then they could implement hardware zeroing rather than require the OS to wait several seconds for charges to fully dissipate.
- std_throwaway 10y agoThe same with sound.
- gsnedders 10y agoIt's also worthwhile pointing out that at the time MS were pushing Silverlight heavily, which provided GPU access through XNA and made itself accessible through a browser plugin by default. MS's security side may have been against WebGL and the IE team either agreeing or using it as an excuse (and really, from this point of view, it doesn't matter!), but other parts of the company were exposing the web to the exact same problems.