Microsoft's Gazelle browser: A layperson's explanation

TalkBack 3 of 20:

Next »

« Previous

• Thread View
• Flat View

IE tab isolation is not the same as Chrome's

IE does use multiple processes. But start IE
restoring 8 tabs from a prior session, and
you'll see that all 8 are loaded into just two
processes.

More importantly, each IE process reads and
writes to the disk and each IE process writes
to the network. There is no security
boundaries between the processes.

Chrome, by contrast, has a browser process
which governs the disk and network IO. Each
tab gets a "sandbox", which is a restricted
permissions OS.

If you read the gazelle paper, they cite Chrome
quite a lot. They're going to one more level,
which is a little deeper. But yeah, Chrome
really pioneered the notion of each-tab-in-a-
separate security sandbox.

This is why IE was hacked at pwn2own and Chrome
was not.

Posted by: mick z   Posted on: 07/05/09 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now
• Open Standards Technologies Provide the Ingredients for Delivering Security Across the Papa Gino's Enterprise Dell Papa Gino's Holdings Corporation founded by the entrepreneur operates one ... Download Now
• Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now