4 ms·

WebGL is a helluva drug. Have they solved or answered the security considerations from letting a website issue graphics commands?

• spot 15y ago
  yes: http://hacks.mozilla.org/2011/06/cross-domain-webgl-textures-disabled-in-firefox-5/ http://hacks.mozilla.org/2011/06/cross-domain-webgl-textures... unless you mean something else...
  • nitrogen 15y ago
    There were also concerns about running arbitrary shader code on the GPU, which has DMA access (Yes, Direct Memory Access access is a bit redundant...) to system memory, as well as the framebuffer which is in GPU memory.
    • spot 15y ago
      only a problem if there's a bug in the drivers. if you can find such a bug, please let me know.
      • ehsanu1 15y ago
        The issue is that if there does happen to be some type of bug which allows an exploit, simply pointing your webgl-enabled web browser at some page would let an attacker compromise your system. This wasn't really a problem before webgl, since to get 3d graphics running at all, an attacker would have had to have code execution privileges on a victim's computer (by which time it's already too late).
        • SoupIce 15y ago
          Precisely. WebGL opens up a whole new can of worms for malware writers. 3D drivers can not be and are not immune to bugs.
        • ehsanu1 15y ago
          SoupIce, you may have been hellbanned.
      • ehsanu1 15y ago
        The issue is that if there does happen to be some type of bug which allows an exploit, simply pointing your webgl-enabled web browser at some page would let an attacker compromise your system. This wasn't really a problem before webgl, since to get 3d graphics running at all, an attacker would have had to have code execution privileges on a victim's computer (by which time it's already too late).