4 ms·
Native client is a horribly bad idea on so many levels. Wiz-bang demos aren't enough to distract from the danger. Now trojans have one huge, lovely target. Jus
by ck2 15y ago
Native client is a horribly bad idea on so many levels. Wiz-bang demos aren't enough to distract from the danger.
Now trojans have one huge, lovely target. Just change browser settings and boom, easy attack. This in combination with hiding everything from users (status bar, url bar, etc.) is super dangerous. It's activex all over again.
Do it in webgl or otherwise, leave native code execution outside the browser.
- jbri 15y agoIn what way is NaCl worse than webgl?
- jbk 15y agoActually it is better for security.
- gcr 15y agoProof please? Whenever I visit a WebGL demo inside Linux w/ NVidia drivers, if there are any complicated shaders, my system hard-freezes, forcing me to reboot. Until the X developers fix Xorg's security model (like that will happen), and until NVidia fixes their Linux drivers (like that will happen), WebGL will always be one massive gaping security and stability problem for me as a Linux user.
- jbk 15y agoSo, you are saying the same thing that I am :D
- iam 15y agoBecause it runs userspace code on x86, instead of running kernel-level code on the GPU?
- jbk 15y agoBecause we know, those days, to sandbox raw x86 code, and not let them access the system and the drivers... However, running shaders directly on the GPU exposes directly graphic drivers, that are not conceived to block unfriendly code.
- angryasian 15y agowhy not hold your pessimism till we actually see something. Security has been a major focal point for NaCl. Until then play some old school games.
- jbk 15y agoWhy so? You don't have access to outside APIs with NaCL.
- nikcub 15y agonative client has the same sandbox and API access as javascript and chrome extensions