3 ms·
As I said in another thread, aren't these security points all applicable to JOGL running in a Java applet? Therefore if they are exploitable, they probably alr
by AshleysBrain 15y ago
As I said in another thread, aren't these security points all applicable to JOGL running in a Java applet? Therefore if they are exploitable, they probably already are being exploited, and therefore implementing WebGL does not add any new attack vectors. Am I wrong?
An interesting question would be "If all these security concerns were resolved, would Microsoft then implement WebGL?". Then, I guess, the answer is still no, because WebGL is based on OpenGL and not DirectX.
- bad_user 15y agoEven if JOGL has the same problems, the blame is not theirs anyway as they aren't distributing Java anymore, otherwise you must blame them for allowing OpenGL on Windows too. "If all these security concerns were resolved, would Microsoft then implement WebGL?" To me that's irrelevant - Chrome and Firefox combined have enough market share to make WebGL useful. What is important to me is if they are right, what are the Khronos Group doing about it? Is WebGL really designed for the web? AND, can it be fixed without relying on companies fixing their drivers or is it a fundamental flaw?
- kragen 15y agoI block Java applets by default, but not JS, and I don't have a way to block only some JS APIs.