BlogsGoogleNative Client and Secure Code Execution

Native Client and Secure Code Execution

Native Client and Secure Code Execution

8
posts
2008–2012

Google's Native Client (NaCl) technology has evolved to enable the secure execution of native code within web browsers. Early efforts focused on establishing the security model and encouraging community participation through contests. Subsequent developments included the availability of Native Client for apps in the Chrome Web Store, allowing developers to bring high-performance native applications to the web. This post announces the beta launch of Google Chrome Extensions, which leverage Native Client to run games, apps, and runtimes directly in the browser, expanding the ecosystem of applications that can be delivered via the web.

2012

A better developer experience for Native Client- Google Developers Blog

10/17/2012

This post introduces improvements to the developer experience for Native Client (NaCl). It highlights the release of a new NaCl SDK that simplifies development by providing a more integrated and user-friendly environment. Key improvements include better debugging tools, easier integration with existing build systems, and enhanced documentation, all aimed at making it more accessible for developers to build and deploy high-performance applications using NaCl.

2011

Games, apps and runtimes come to Native Client- Google Developers Blog

12/9/2011

This post announces the beta launch of Google Chrome Extensions, which leverage Native Client (NaCl) to run games, apps, and runtimes directly in the browser. This expands the ecosystem of applications that can be delivered via the web, building upon the existing security model and community participation efforts for Native Client.

Native Client brings sandboxed native code to Chrome Web Store apps- Google Developers Blog

8/18/2011

This post announces the availability of Native Client for apps in the Chrome Web Store, enabling developers to bring high-performance native applications to the web by allowing the execution of sandboxed native code.

Native Client: Getting ready for takeoff- Google Developers Blog

2/18/2011

This post announces that Native Client (NaCl) is nearing production readiness, with a focus on stability and performance improvements. It highlights the ongoing work to make NaCl a robust platform for running native code in the browser, suggesting that the technology is moving beyond its experimental phase and towards wider deployment.

2009

Google Chrome Extensions launched in beta!- Google Developers Blog

12/8/2009

This post announces the beta launch of Google Chrome Extensions. These extensions leverage Native Client (NaCl) to allow developers to build installable applications that run within Chrome, offering enhanced functionality and richer user experiences. This represents a significant step in enabling developers to create more powerful and integrated applications directly within the browser environment.

Native Client Security Contest: The results are in!- Google Developers Blog

7/7/2009

Announces the results of the Native Client Security Contest, highlighting the successful identification and patching of vulnerabilities. This demonstrates a proactive approach to securing the Native Client platform and building trust with developers.

Announcing the Native Client Security Contest- Google Developers Blog

2/25/2009

This post announces the Native Client Security Contest, a program designed to identify and address security vulnerabilities in the Native Client technology. This initiative aims to foster community participation in improving the security and robustness of the platform.

2008

Native Client: A Technology for Running Native Code on the Web- Google Developers Blog

12/8/2008

This post announces the beta launch of Google Chrome Extensions, which leverage Native Client (NaCl) for running native code on the web. It highlights the potential for high-performance applications and introduces the security model and development process for NaCl.