Gazelle relies on a ‘browser kernel’ that could offer far greater security than Google’s Chrome, Mozilla’s Firefox, or Microsoft’s own Internet Explorer
Gazelle also aims to limit the dangers posed by programming flaws in browser plug-ins. Plug-ins are small bits of code that enable other programs to run within a browser, but they’ve also been known to contain vulnerabilities that can allow a PC to be hacked.
Oracle White Paper - Nucleus Report: Who’s ready for SMB? - read this white paper.
In Gazelle, the plug-ins are sandboxed, or isolated from the rest of the system, so that a bad plug-in would only affect the particular Web page’s plug-in process and not the whole PC.
But one huge problem with Gazelle’s approach is that existing plug-in code would have to be rewritten or ported to interact with Gazelle’s browser kernel system calls. That’s difficult since plug-ins are written by a wide variety of software vendors whose development schedules don’t necessarily work in perfect sync with those of browser developers.
Other parts of Gazelle borrow from IE code not related to security. For example, the researchers said they didn’t want to write a new HTML parser, so they used IE7’s Trident renderer and JavaScript engine.
In compatibility tests, Gazelle correctly rendered 19 of the top 20 sites ranked by Web survey firm Alexa. The paper warns that the new security of Gazelle does introduce “performance overhead” — especially for sites such as the New York Times Web site — but further work should be able to make it faster.