5 ms·
If this worries you go ahead and disable WebGL too.
by bcoates 8y ago
If this worries you go ahead and disable WebGL too.
- zokier 8y agoFrankly, might not be such a bad idea. https://www.contextis.com/blog/webgl-more-webgl-security-flaws https://www.contextis.com/blog/webgl-more-webgl-security-fla... etc
- mirimir 8y agotl;dr > However, to enable this impressive breakthrough in online technology, web browsers (currently Chrome and Firefox) have had to expose low level parts of their operating systems which previously could not be directly accessed by potentially malicious web pages, thus creating a number of potential security vulnerabilities.
- greggman 8y agoyour post is FUD. that issus was solved immediately and the actually bug listed had nothing special to do with graphics and is just a bug like a bug in javascripy or the browser in general. a bug that was fixed. If you're going to off WebGL based on that bug then you'd better turn off your entire browser
- mirimir 8y agoI do. It's a fingerprinting risk, if nothing else.
- greggman 8y agoChrome itself doesn't have these issues. In particular it doesn't support features that would raise these kinds of issues. For one it's not supporting all of desktop opengl it's only supporting the subset that needed for WebGL. All of if is massively validated , shaders are rewritten, bound checked, memory cleared, clamps added, etc...
- greggman 8y agolove the ignorant downvotes. I wrote the chrome GPU subsystem. if you have evidence that I'm wrong post it. otherwise your just spreading FUD