Native Client and Secure Code Execution

8 posts · Dec 2008 – Oct 2012

What this trail covers

Google's Native Client (NaCl) technology has evolved to enable the secure execution of native code within web browsers. Early efforts involved the Native Client Security Contest to identify and address vulnerabilities, demonstrating a commitment to robust security. Subsequent developments have involved expanding NaCl's capabilities, improving its performance, and integrating it into more Google products and services to enable high-performance web applications.

All Google trails

Oct 2012A better developer experience for Native Client- Google Developers BlogThis post announces the beta launch of Google Chrome Extensions, which leverage Native Client (NaCl) to enable the secure execution of native code within web browsers. This aims to improve the performance and security of web applications by allowing developers to bring high-performance native applications to the web.
Dec 2011Games, apps and runtimes come to Native Client- Google Developers BlogThis post announces the beta launch of Native Client, enabling games and applications to run at near-native speeds within the Chrome browser. It highlights the potential for high-performance applications and games to be developed and deployed via the web.
Aug 2011Native Client brings sandboxed native code to Chrome Web Store apps- Google Developers BlogThis post announces the beta availability of Native Client (NaCl) for Chrome Web Store applications. It highlights that NaCl allows developers to bring sandboxed native code to Chrome, enabling high-performance applications that were previously not feasible in a web browser. The post emphasizes the security benefits of NaCl's sandboxing mechanism and its potential for enabling new types of web applications.
Feb 2011Native Client: Getting ready for takeoff- Google Developers BlogThis post announces the beta launch of Native Client (NaCl), making it available for developers to test and use. It highlights the security benefits of NaCl, emphasizing its sandboxing capabilities that allow native code to run securely within the browser. The post encourages developers to experiment with NaCl and provide feedback, signaling a move towards wider adoption and integration of the technology.
Apr 2010HTML5 + Quake II- Google Developers BlogThis post announces the successful porting and execution of the Quake II game engine within a web browser using Google's Native Client (NaCl) technology. It demonstrates the capability of NaCl to run complex, performance-intensive applications, including 3D games, directly in the browser, showcasing advancements in secure code execution and web application capabilities.
Advertisement
Dec 2009Google Chrome Extensions launched in beta!- Google Developers BlogThis 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.
Jul 2009Native Client Security Contest: The results are in!- Google Developers BlogAnnounces the results of the Native Client Security Contest, highlighting the identification and resolution of vulnerabilities. This post signifies a critical step in establishing the security and robustness of the Native Client technology for executing native code within web browsers.
Feb 2009Announcing the Native Client Security Contest- Google Developers BlogAnnounced the Native Client Security Contest, a program designed to identify and address security vulnerabilities in Native Client (NaCl). This contest aimed to foster community involvement in improving the security of NaCl, a technology for running native code in web browsers.
Dec 2008Native Client: A Technology for Running Native Code on the Web- Google Developers BlogIntroduced Native Client (NaCl) as a technology for running native code (compiled from C/C++) directly within web browsers. This technology aims to provide near-native performance for web applications by allowing them to leverage compiled code while maintaining security through a sandboxing mechanism. The initial focus is on enabling high-performance applications like games and media players on the web.