42 ms·
Google nabs Square Enix and other game developers for native client Chrome games
- rakkhi 15y ago//Black hat on The main concern for me with native client is webgl and the exposure of 3D device drivers to the Internet. These drivers were not written with this use in mind there have been webgl vulnerabilities in the past: http://www.contextis.com/research/blog/webgl2/ http://www.contextis.com/research/blog/webgl2/ While Google will be aware of these and actively working to provide a buffer with via validation and sandboxing, with pessimistic hat on, I can see this leading to a lot more security vulnerabilities.
- tptacek 15y agoThat's a valid concern; I know another HN user who might chime in with more detail to back it up. On the other hand, Google has built a particularly good security team for low-level systems code problems like this, and they've done things (like the NaCL security contest) to attract the right kind of attention from researchers.
- daeken 15y agoI'm not the least bit concerned about NaCl's involvement here, but I'm still deeply scared by the potential for things to go very badly in the lower levels (but not enough so that I'm willing to disregard the benefits of these APIs, mind you). What it comes down to is that current GPUs do whatever you want with no concern for security; that part depends on the driver and userspace 3d stack. This isn't necessarily bad, but GPU manufacturers can't write code. Bounds checking and all that are pretty well covered by things like ANGLE (translates OGL to D3D on windows and acts as a sanity checker and shader validator everywhere else) but that doesn't help you if, say, your driver improperly compiles valid-but-malicious code. Avenues like that are effectively not researched at all.
- nkassis 15y agoIt's a concerned but it's something GPU vendors are claiming they are working on. There has been moves to improve driver security through the ARB_robustness extension and for the browser vendors there is the ANGLE's project as you have said but also plain blacklisting dangerous cards or drivers. The reality is that web 3D's time seems to have arrived. It doesn't matter if it's through WebGL, Flash, Unity the issue you raised is present in all those solutions. Even Native client has that potential if the sandbox is not watertight. In all, if we want a more capable web these are risk I feel are worth taking. But that's my personal view.
- daeken 15y ago> There has been moves to improve driver security through the ARB_robustness extension IMO, GL_ARB_robustness is almost completely worthless. The one thing it gives you is the ability to time out rendering, in effect, which of course prevents certain types of DoS attacks. There are many other provisions in the extension, but those are already universally implemented in ANGLE and the like; they don't do anything to help with the security of the lower level. > The reality is that web 3D's time seems to have arrived. It doesn't matter if it's through WebGL, Flash, Unity the issue you raised is present in all those solutions. Even Native client has that potential if the sandbox is not watertight. NaCl has the same issues regardless of the sandbox, but I agree entirely: hardware accelerated 3d on the web is worth the risk we'll be dealing with for the first couple of years. I've stopped writing desktop 3d software/demos entirely in favor of WebGL simply because I believe so much in it, but it's not stopping me from doing security research into it as well. At the end of the day, I'm convinced that a reasonably skilled attacker could do terrible, terrible things to my system via WebGL. But the benefits outweigh the risks for me.
- pmjordan 15y agoVirtualisation's rise in popularity has caused IOMMUs to start showing up even in some consumer chipsets. Do you think an IOMMU and a driver that supplies it appropriately restrictive page tables for the GPU will be enough or do we realistically need GPUs with some kind of native memory protection support that can somehow be intertwined with the CPU's process model?
- drivebyacct2 15y agoI wonder how much Google feels comfortable with this level of risk due to the speed with which they are able to push out updates and the rate at which their clients autoupdate themselves.
- evmar 15y agoYour concern is valid, but I believe Native Client doesn't expose any more (GL) attack surface than JavaScript-based WebGL does.
- daeken 15y agoIiiiinteresting. They mention Bastion, which is built with XNA and C#. I wonder how they plan on porting it.
- natfriedman 15y agoBastion runs on Mono, and Mono runs on native client (including the JIT, which required some special work in native client itself). Actually all three apps they demo'd running on native client were also running on Mono!
- daeken 15y agoOh wow, nice. The original version of NaCl didn't allow any runtime codegen -- when did that change?
- bradchen 15y agoHave a look at our 2011 PLDI paper. You can find a link here: http://www.chromium.org/nativeclient/reference/research-papers http://www.chromium.org/nativeclient/reference/research-pape...
- kevingadd 15y agoDo you know what the solution was for XNA? The last time I checked, all the Mono XNA ports were in miserable shape. Considering Bastion makes use of shaders and mixed mode 2d/3d rendering, it seems like it must be running on a high quality port of a large portion of the XNA stack.
- kevingadd 15y agoReplying to provide follow-up detail: I dug into the executables and it looks like it uses OpenTK for rendering and FMod to sound, instead of using a port of XNA. Both are freely available, so that's a pretty simple path to doing a similar port for other XNA games. Neat.
- 15y ago
- zobzu 15y agoThere you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
- Karunamon 15y agoThe major difference being that Microsoft has a history of anticompetitive behavior and google does not. Your unfounded wharrgarble is noted, though.
- zobzu 15y agoGoogle is very similar. They do open up a lot of stuff, and provide a lot of free stuff too. They have a lot of talented people as well. But their base strategy is to control our most powerful tool. For that you need to kill standards. And hey, talented people sure know how to put things on the right balance, at the right time. I'm not sure who you think can compete with Google. For most people "the internet" is Google.com. Google.com tells you to get Chrome. Most top 10 downloaded software bundle Chrome, often with default optin and even default launch. Companies which aren't big enough to fight are bought out. See a trend? What's funny is that my comment gets back to 0 or 1 then back to minus and so on. What it shows is that this is controversial and many actually agree with my "wharrgarble". Maybe you should give it a deeper though. We'd be better in 5 years from now, if everyone though about such things with a little more criticism.
- nkassis 15y ago"I'm not sure who you think can compete with Google. For most people "the internet" is Google.com." I thought the meme was that for most people facebook.com is the web? All Google cares about is that whatever tech is out there doesn't prevent them from displaying Ads to as wide an audience as possible. This is a very different motive than what Microsoft has which is to control your entire PC experience.
- freehunter 15y ago
- deleted 15y ago[deleted]
- carldall 15y agoRegarding Native Client: I don't think that Google is evil just because they try to move web technologies forward in non w3c standardized ways, and I don't even want to go into this discussion because there're (imho) valid arguments for both sides, But: For web developers, this whole process is suboptimal to say the least. It only adds to the already existing complexity of the web technology stack but enforces more browser checks and fallbacks. Even worse, as soon as you're working for a customer who isn't technical, you'll land in a situation where he shows you a Native Client app and wants "something like that" on his website but running in Firefox or Safari or (even worse) Internet Explorer.
- tantalor 15y ago"To nab" means "to sieze", which implies Google bought out Square Enix. Better title might be, "Google taps Square Enix".
- primigenus 15y agoThe advent of Native Client combined with this move means the Chrome Web Store is going to end up positioned as a direct competitor to Steam. That's pretty interesting, honestly. It'll mean great things for consumers: I bet playing a game in your browser could be really convenient compared to downloading and installing Steam and then going through the motions for that platform. But Steam has 7 years on the Web Store with all kinds of great platform features like Steam Play, Cloud, Wallet, etc. An exciting time to be a web and game developer, to be sure!
- melling 15y agoHow does native client solve the ARM vs Intel issue? Can a fat binary be created so apps run on both an ARM Chromebook and an Intel PC? Finally, can native client be adopted by Opera and Apple for use in their browsers?
- azakai 15y agoNative Client does not solve the portability issue. Portable Native Client is a research project trying to do that, but it is unclear whether it will succeed, and if it does, with what compromises (speed, security, etc.) Native Client can in theory be adopted by other browsers, since it is open source, however no other browser has shown interest, the opposite in fact. Native Client is a nonstandard technology that will remain only in Chrome.