Thursday, July 16, 2009

GooGle Crome

Google crome

Google crome

It is a new web browser developed by google.
A beta version for Microsoft Windows (XP and later only) was released on 2 September 2008 in 43 languages. Mac OS X and Linux versions are under development.

The first release of Google Chrome passed the Acid1 and Acid2 tests. While it has not yet passed the Acid3 test, Google Chrome scored 78/100—higher than both Internet Explorer 7 (14/100) and Firefox 3 (71/100), but lower than Opera’s 84/100. When compared to equivalent “preview” or beta builds, Chrome scored lower than Firefox (85/100), Opera (91/100), and Safari (100/100), but still higher than Internet Explorer (21/100).

Chromium releases :

On 15 September 2008, CodeWeavers released an unofficial bundle of a WINE derivative and Chromium Developer Build 21 for Linux and Mac OS X, which they dubbed “CrossOver Chromium” An unofficial workaround for use with Windows 2000 is also available.

Design :

Primary design goals were improvements in security, speed, and stability compared to existing browsers. There also were extensive changes in the user interface.[8] Chrome was assembled from 26 different code libraries from Google and others from third parties such as Netscape.

Security :

Chrome periodically downloads updates of two blacklists (one for phishing and one for malware), and warns users when they attempt to visit a harmful site. This service also is made available for use by others via a free public API called “Google Safe Browsing API”. In the process of maintaining these blacklists, Google also notifies the owners of listed sites who may not be aware of the presence of the harmful software.
Chrome will typically allocate each tab to fit into its own process to “prevent malware from installing itself” or “using what happens in one tab to affect what happens in another”, however the actual process allocation model is more complex. Following the principle of least privilege, each process is stripped of its rights and can compute, but can not write files or read from sensitive areas (e.g. documents, desktop)—this is similar to “Protected Mode” that is used by Internet Explorer 7 on Windows Vista. The Sandbox Team is said to have “taken this existing process boundary and made it into a jail”;[26] for example, malicious software running in one tab is unable to sniff credit card numbers, interact with the mouse, or tell “Windows to run an executable on start-up” and it will be terminated when the tab is closed. This enforces a simple computer security model whereby there are two levels of multilevel security (user and sandbox) and the sandbox can only respond to communication requests initiated by the user.
Typically, Plugins such as Adobe Flash Player are not standardized and as such, cannot be sandboxed as tabs can be. These often need to run at, or above, the security level of the browser itself. To reduce exposure to attack, plugins are run in separate processes that communicate with the renderer, itself operating at “very low privileges” in dedicated per-tab processes. Plugins will need to be modified to operate within this software architecture while following the principle of least privilege.Chrome supports the Netscape Plugin Application Programming Interface (NPAPI), but does not support the embedding of ActiveX controls. Also, Chrome does not have an extension system such as Mozilla’s XPInstall architecture. Java applets support is available in Chrome as part of the pending Java 6 update 10, which currently is in Release Candidate testing.

A private browsing feature called Incognito mode is provided as well. It prevents the browser from storing any history information or cookies from the websites visited. This is similar to the private browsing feature available in Apple’s Safari and the latest beta version of Internet Explorer 8.

The current beta uses an old version of WebKit – 525.13 – which is actually the same WebKit engine used by the old Safari v3.1. The current Safari version is v3.1.2, which fixed several critical issues, including the “blended threat” Carpet Bombing vulnerability. Google even mention that they use Safari v3.1 rendering engine in their own documentation.

No comments:

Post a Comment