Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Thread beginning with comment 552458
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Comment by ssokolow
by cdude on Fri 15th Feb 2013 00:12
in reply to "RE[7]: Comment by ssokolow"
Come on. We all, that have a little technical knowledge, know Microsoft spreads its usual FUD.
http://games.greggman.com/game/webgl-security-and-microsoft-bullshi...
http://blog.jprosevear.org/2011/05/13/webgl-security/
http://www.khronos.org/webgl/security/#Conclusion
And for your Silverlight case. This is brand new Microsoft technology that does EXACT the same WebGL does but only on Windows. Lock-in. Its in Windows Phone 7 and its in Windows Phone 8.
Also you not seem to know that IE10 uses an hw-accelerated canvas. Security danger!!!1!
Edited 2013-02-15 00:16 UTC
RE[9]: Comment by ssokolow
by lucas_maximus on Fri 15th Feb 2013 14:51
in reply to "RE[8]: Comment by ssokolow"





Member since:
2009-08-18
Conjecture. I wonder why we have our browsers patched by every company with security vunerabilities. Nothing is secure and WebGL is insecure by design as the article states, IF YOU ACTUALLY READ IT!
ActiveX is off these days by default unless it is a trusted plugin, much like flash. I suspect silverlight is the same. This isn't 2004 anymore.
Find arguments that aren't over 8 years old please.
The biggest security thread to browsers has been the Java Plugin for years now.
From the penetration testing company, which I dunno actually make money doing this stuff.
Context therefore recommends that users and system administrators disable WebGL.
Sorry I am going to take a penetration testing companies' word over yours.
Edited 2013-02-14 17:36 UTC