Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Opera Software De kogel is door de kerk: as we already talked about earlier, Opera is going to switch to the WebKit engine, leaving its own Presto rendering engine behind. We didn't yet know if they would the switch only on mobile or on the desktop as well, and they cleared that up too: both mobile and desktop Opera Browsers will switch to the WebKit rendering engine.
Thread beginning with comment 552458
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Comment by ssokolow
by lucas_maximus on Thu 14th Feb 2013 17:34 UTC in reply to "RE[6]: Comment by ssokolow"
lucas_maximus
Member since:
2009-08-18

Fact is Firefox, Chrome are both way more secure then IE. Fact is Firefox, Chrome, both implement WebGL, IE doesn't. So?


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!

And come on, Microsoft crying about WebGL security while doing ActiveX and Silverlight can't be taken serious.


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.

For native, direct access to hardware. Compiled Javascript, eg V8 and WebCoreScript, native code, all do. Its not magic but pretty standard.


From the penetration testing company, which I dunno actually make money doing this stuff.

It would be unreasonable to expect full conformance to the complete specification of a new standard: there are always likely to be edge cases. But, as we have stressed before, some areas of WebGL need to be carefully implemented to prevent security issues arising and unfortunately in this case, because security-related conformance tests are not clearly identified, it is not possible to determine if an implementation is secure. This has been a contributory factor in security issues being missed by developers of the current browser implementations of WebGL, which has in turn created serious security flaws. Browser developers should start banning non-conformant configurations as they are identified until the security issues that have been highlighted are resolved.

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

Reply Parent Score: 3

RE[8]: Comment by ssokolow
by cdude on Fri 15th Feb 2013 00:12 in reply to "RE[7]: Comment by ssokolow"
cdude Member since:
2008-09-21

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

Reply Parent Score: 2

RE[9]: Comment by ssokolow
by lucas_maximus on Fri 15th Feb 2013 14:51 in reply to "RE[8]: Comment by ssokolow"
lucas_maximus Member since:
2009-08-18

Actually more FUD these days is spread by the open source community.

TBH I am pretty sure you would argue black was white if it somehow involved Microsoft.

Reply Parent Score: 3