Mozilla Concerned About Google Chrome Frame

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
Looks like Microsoft isn’t the only company that is concerned about Google’s Chrome Frame, according to this eWeek article. However, while MS tries to play the security angle, Mozilla is uneasy about the possibility that Frame will “further muddy the already cloudy waters” of the browser market.

"The user's understanding of the Web's security model and the behavior of their browser is seriously hindered by delegating the choice of software to the developers of individual sites they visit," Shaver wrote. "It is a problem that we have seen repeatedly with other stack plug-ins like Flash, Silverlight and Java, and not one that I think we need to see replayed again under the banner of HTML5."
 
This is kinda another security angle too. If a malicious website knows there's a vulnerability in chrome they can exploit, they can specifically call for it to be used if it's installed on the users system even if they're not actively using that browser and possibly bypassing other browser security models like the IE7/8 sandboxing. I'm pretty sure I don't like the idea that a website can say "load us up in browser X because we know we can exploit it, whether you like it or not".
 
This is kinda another security angle too. If a malicious website knows there's a vulnerability in chrome they can exploit, they can specifically call for it to be used if it's installed on the users system even if they're not actively using that browser and possibly bypassing other browser security models like the IE7/8 sandboxing. I'm pretty sure I don't like the idea that a website can say "load us up in browser X because we know we can exploit it, whether you like it or not".

Then you wouldn't have to use it, I think it's a great idea for people stuck with IE6 on locked corporate machines where they only have access to install browser plugins.

That said, the Mozilla argument is a lot sturdier than the Microsoft argument based solely on the premise that security is additive, since it's a plug-in, by assuming there are security concerns, they basically admit fault in their own browser architecture.

On the other hand, further dissociating the user from the way in which their software works could be a dangerous thing. Or it could turn out to be an amazing thing that we will take for granted in the future when web applications just work.

I must say that I think Google's real goal here is to push HTML5 further and faster so it can start pushing out apps that use it.

You can discuss the merits all you want, but until it's in the wild and utilized, no one really knows. Let it happen and see if it's for you. Prejudice is pointless.
 
Back
Top