Caja project
In this article we are going to analyze in depth Caja project, a topic of great relevance and interest today. From its origins to its impact on today's society, Caja project has generated debate and growing interest among experts and the general public. Throughout the next few lines we will explore the different aspects surrounding Caja project, from its historical importance to its influence in different areas of daily life. Additionally, we will examine different perspectives and opinions about Caja project, with the aim of offering a complete and objective view of this topic.
Caja (pronounced /ˈkɑːhɑː/ KAH-hah) was a Google project for sanitizing third party HTML, CSS and JavaScript. On January 31, 2021, Google archived the project due to known vulnerabilities and lack of maintenance to keep up with the latest web security research, recommending instead the Closure toolkit.
The Caja project was led by Jasvir Nagra with the JavaScript portion designed by Google research scientist Mark S. Miller in 2008 as a JavaScript implementation for "virtual iframes" based on the principles of object-capabilities. It would take JavaScript (technically, ECMAScript 5 strict mode code), HTML, and CSS input and rewrite it into a safe subset of HTML and CSS, plus a single JavaScript function with no free variables. That means the only way such a function could modify an object, was if it was given a reference to the object by the host page. Instead of giving direct references to DOM objects, the host page typically gives references to wrappers that sanitize HTML, proxy URLs, and prevent redirecting the page; this allowed Caja to prevent certain phishing and cross-site scripting attacks, and prevent downloading malware. Also, since all rewritten programs ran in the same frame, the host page could allow one program to export an object reference to another program; then inter-frame communication was simply method invocation.
The word "caja" is Spanish for "box" or "safe" (as in a bank), the idea being that Caja could safely contain JavaScript programs as well as being a capabilities-based JavaScript.
Caja was used by Google in its Google Apps Script products. In 2008 MySpace and Yahoo! had both deployed a very early version of Caja.
See also
References
- ^ Mark, Miller. "Caja discussion on the Caplet Group". . . Archived from the original on 17 May 2008.
- ^ "Introduction - Caja". Google Developers. Archived from the original on 22 January 2021.
- ^ Miller, Mark S.; Samuel, M; Laurie, B; Awad, I; Stay, M (7 June 2008). "Safe active content in sanitized JavaScript". Google Scholar.
- ^ Synodinos, Dio (25 February 2011). "ECMAScript 5, Caja and Retrofitting Security, with Mark S. Miller". InfoQ.
- ^ "Html Service: Caja Sanitization". Google Developers. Archived from the original on 26 August 2013.
- ^ "MySpace: Caja JavaScript scrubbing ready for prime time". 4 February 2008. Archived from the original on 1 October 2008.
- ^ "Web 2.0 Investors: Pay Attention To Caja". Tim Oren's Due Diligence. 11 April 2008.
- ^ Pullara, Sam (28 October 2008). "OpenSocial API Blog: Launched: Yahoo!'s First Implementation of OpenSocial Support". OpenSocial. Archived from the original on 16 December 2008.
External links
- Caja project home page
- Caja project source code
- Caja playground
- Caja draft specification: "Safe active content in sanitized JavaScript", Mark S. Miller, Mike Samuel, Ben Laurie, Ihab Awad, Mike Stay
- Yahoo!/Google Caja Javascript Sandbox
| Dialects | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Engines (comparison) | |||||||||
| Frameworks |
| ||||||||
| People |
| ||||||||
| Other | |||||||||
| |||||||||
