Google Barks Back At Microsoft Over Chrome Frame Security
CWmike writes "Google hit back at Microsoft on Friday, defending the security of its new Chrome Frame plug-in and claiming that the software actually makes Internet Explorer safer and more secure. 'Accessing sites using Google Chrome Frame brings Google Chrome's security features to Internet Explorer users,' said a Google spokesman today. 'It provides strong phishing and malware protection, absent in IE6, robust sandboxing technology [in IE6 and on Windows XP], and defenses from emerging online threats that are available in days rather than months.' On Thursday, Microsoft warned users that they would double their security problems by using Chrome Frame, the plug-in that provides better JavaScript performance and adds support for HTML 5 to Microsoft's browser."
The company is also investigating bugs filed with the Chrome team by Microsoft developers, who reported that Chrome Frame broke IE8's privacy mode.
Why am I not surprised this feature wasn't tested at Google? ;)
But on an interesting note, this seems to be a direct attack against Microsoft by Google. Granted not that many users will probably install it (especially 'normal' users who just dont care), with this and Chrome OS it's clear that Google is going after MS.
Also, this is another avenue for Google to datamine everything about the internet. People dont usually think about it, but Google's analytics traffic code is all over the internet and probably 90% of the sites you visit is known to google. Another interesting thing is that Slashdot used to hide the tracking code under its own domain, so just blocking the analytics domain didn't work.
While I dont like some of the business practices by neither one, its hard to pick sides here. Atleast MS sells the products directly, while Google monetarizes them by ads. And by that very nature you lose lots of privacy.
Earlier there was also discussion that Chrome Frame is mostly provided for corporate users who are required to use IE and cant install other browsers. But how can they install this plugin then? It's normal exe and probably requires even more admin rights to get inside IE than just installing Chrome on your userbase. And other than that I dont see a point in wrapping another browser plugin to work inside browser. If people are knowledge about this plugin, they're knowledge about the actual Chrome browser too. And IE user experience and GUI sucks.
"It provides strong phishing and malware protection, absent in IE6, robust sandboxing technology [in IE6 and on Windows XP], and defenses from emerging online threats that are available in days rather than months."
Irrelevant. The point is that it's another exploitable object, thereby expanding the exposed surface of attack. That's Microsoft's entire point. There's just no reason to get this installed in corporate networks where IE6 is being used (breaks most intranet sites), anyplace where IE7 is being used (there's IE8; upgrade to it), and anyplace where IE8 is being used (surface of attack expanded in exchange for little benefit). Downloading Chrome itself is fine, but this is nothing more than a veiled attempt at tricking users into using Chrome instead of legitimately gaining marketshare.
Viable Slashdot alternatives: https://pipedot.org/ and http://soylentnews.org/
Despite being a user of Vista, Zune, and a former XBOX owner, I'm not overly fond of Microsoft's stance on software. Zune needs to be open sourced so developers and modders can start creating utilities for it that matter. Microsoft adopted a "we-will-handle-it-ourselves-and-drag-the-competition-under-our-wheels" approach to software and the way the internet should be "browsed." As such, everyone is commiting herecy and blasphemy when they try to make a better program for the same function that Microsoft's software already does. For instance, look at Linux. Although it's not quite as compatible for gaming as Windows is, more and more gamers are turning to Linux, quite simply for the ease of use, and the fact they can modify their installations to fit their needs. Even down to programming something for it. All Google is guilty of, besides being asses about Android, is making a perfectly legitimate program and essentially offering to keep on top of it ("...and defenses from emerging online threats that are available in days rather than months") better than even Microsoft does. Do I smell corporate greed?
"Chance favors only the prepared mind." -Archimedes
I'm thinking that IE users' primary concern is not security or they'd be using something else to begin with.
To run with your Aircraft Carrier vs Leaky row boat analogy...
This is more akin to putting a nuclear powered steam turbine engine from an air craft carrier into your leaky row boat.
Sure, it'll make your leaky row boat fast as hell and able to pull huge objects, but your leaky row boat is still leaky, over weight, and now requires a constrant stream of fuel.
The GP's point is in part accurate. CF does indeed increase the exposed surface of IE. If you are willing to live with that risk, do it, if not, don't.
I also find it odd that Google was complaring it to IE6. Isn't that kinda like MS comparing IE8 with Chrome Alpha or Fire Fox 1.0? The only option for IE6, IMO, is to get rid of it. Developers need to abandon support for it, force users to upgrade to IE8, or to switch to FF or Chrome. But comparing their plug-in with an 8 year old browser is disengenuous.
-Rick
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
The new motto in Microsoft is "Windows 7 is not done, until Chrome Frame wont run".
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
I'm a Firefox / Chrome fan and I just installed the Google Chrome Frame to see how it behaves. I installed Windows XP SP2 less than 24 hours ago and since then I've only installed my drivers, Firefox and the Google Chrome Frame; I went to a couple of innocent websites with IE6 and they both crashed the browser.
PS: Web developer here - Yes, IE6 sucks but it is not THAT unstable.
Your posting is rejected because you included an aircraft carrier analogies. To be standard compliant for slashdot users, please reframe it as a car analogy.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Microsoft: Making that claim - double security issues - in some countries would get you into very hot water. MS has not said much about Adobe, who has a not so good (security) track record.
Clearly any hacker will avoid Google addins like the plauge (because they will be fixed fast), and go for the nice, static, unpatched MS code.
The likely NEW risks are those in the code path of new HTML5 features and functions, and not the plugin.
Whatever MS's whinges, Google will fix it. MS is probably doing a mental, as Yahoo like plugins will come After Chrome. We have seen MS use policy to favor its own product/family before, so Google doing the same is not news - but it is also not a security thing.
Fear not!
Google has released a plug-in that automatically converts non-compliant analogies on Slashdot into either car or house-front-door-unlocked analogies
I believe it can optionally do automated library of congress conversions as well as append random critique regarding the nature of Slashdot's CSS.
So Google "barks back" but Microsoft "hits back"?
I tested this plug-in:
I don't know about making it less secure, but it sure causes a bunch of "recovered" tabs and multiple errors.
Not Ready for Prime Time!
Politics is the art of looking for trouble, finding it everywhere, diagnosing it incorrectly and applying the wrong fix.
Microsoft has nothing to gain in this war of wards. They should have known it before they started it: now Google has more than just an excuse to publicize/raise the awareness of IEs security holes, educating the public on phishing, in the process. This will will definitely raise the interest of at least some IE users who would have not otherwise bothered themselves with Google's add-on.
I can see how MS got suckered into this, though: they just can't stand someone walking into their turf. Their predator instinct is just too strong, and makes them do stupid things.
Well played, Google.
"The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
Google is at war and its goal is the liberate the browsers and allow them to be everything they can be.
Evil Microsoft has poor IE as a hostage and is doing terrible things with it. It could be so much but forced into ghetto conditions it is backwards and idiotic.
Direct war with the evil Microsoft is hard but Google is dropping supplies behind enemy lines to help as much as possible. Luxuries other browsers can take for granted are dropped in the form of javascript libraries so that IE can still at least somewhat come along no matter how slow.
Now with this new weapon of peace the evil Microsoft can be twarthed like never before, every IE that dares can now be free and standup like a real browser with all the features those in the free world have come to taken for granted.
There is not going to be one single succesful strategy to liberate the browser, but liberated it will be. Google needs freedom more then any true american company needs air to breath. The communist Microsoft (All for one OS and one OS for all) shall be vanquished. It will not happen overnight, but it will happen.
For the humor impaired: Google needs fast capable browsers because that is where it does its business. If MS can't produce a capable browser then it got 3 options: advertise other browser (firefox), produce its own to push the cutting edge (Chrome forced firefox to become quicker) and to augment the least capable browsers to support current standards. It will have to push hard from different directions to achieve this but success has already been made. MS has had to work very hard with IE and you can see from their response about this plugin in that they are very scared indeed about the browser becoming more capable.
This battle is NOT about getting people to install Chrome or Firefox, it is about having them surf the web with a capable browser so Google can push new features and not have to constintly cripple their application for an obsolete piece of software.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
Goggle should stop pussy-footing around and add a warning box to thier mainpage that tells a user how many publicly announced unpatched exploits there are for the users browser & os. or "Microsoft press statement" => did you mean lies?
IranAir Flight 655 never forget!
Did they expect something like "Thank you google for fixing some of the problems we had on a browser we don't want to code for anymore" ?
Cause it's true they face new security problems that won't be fixed by microsoft with monthly critical updates as it is a plugin and not the basic application.
what the fuck is Win97, you cocksucker???
It's like you are talking a different language, can you use a car analogy please?
I share everyones passionate hate against IE especially since I have to run a Virtual emulator to run that IE (for testing sites) but entering a browser that way, relying on a meta flag which can be implemented by anyone and trusting users to differentiate between a browser engine and UI sounds too much to me.
I believe users need exact same rights to install a browser rather than a ActiveX control so they better advertise their browser instead of plugging into others. They should also check the market for why exactly their browser isn't that much used, why some users have very serious privacy concerns about them lately and why a certain team at Google insists on driving people and companies nuts by insisting on that absurd "updater" policy.
What if MS plugged into Google browser and enabled IE engine whenever a site looks for IE? This has no end. People can't differentiate between an engine and a UI, even on slashdot you see comments like "but Safari is closed source", think about ordinary users and who will they contact when Google engine fails browser?
... the website has to include a meta-tag indicating that the site should be displayed in Chrome Frame instead of IE ...
The very last thing I want as a system administrator are hundreds of thousands of sites (if not millions, or more) requiring the user to have Google Chrome, or the Chrome Frame plugin, before the site can be used. Web sites should be designed using web standards, and not require specific browsers for use. Talk about pot calling kettle black! Plugins should be handlers for the primary browsers functions, not over reaching take over my browser leaches.
When is google going to come out with "chrome frame for firefox beta"? Or when is goggle going to talk about how firefox .8 does not suport the standerds as well as chrome.
That is what this sounds like to me. this plugin is to help IE 6. that is years old.
You mean what if Microsoft released a plugin and required it to be installed for some of their sites to work properly? I don't know, I can't think what would happen in that case; probably people would just install the plugin and let it take over running the web app.
I am TheRaven on Soylent News
I wish it weren't so, really. It's an abomination and we knew it when the thing was released, but there it is. Friends don't let friends use IE6. It's common and more reasonably secure browsers aren't supported on sites that require IE6. Enterprises need IE6 for intranet sites and they can't afford to or aren't able to rewrite sites to adhere to standards.
They could choose to fix this problem by requiring their development teams to adhere to standards, but that's not the direction they're going -- instead the job ads are full of requirements that for successive iterations of Microsoft deprecated versions of .net. The persistence of stupidity is remarkable, but that's a different topic.
This paradigm is inherently flawed: the network is not a trusted environment and in that environment a Windows server should be the least trusted element. Microsoft themselves admit this when they force you to choose between the latest version of their server operating system or the latest version of their mail server, but not both, putting you in the position of choosing either an OS that's currently as secure as it can be, or a mailserver that is, but not both.
So what can you do? The Google solution actually looks like a good answer at first, but then realize that it enables and empowers people to continue using a browser that's known to be bad. If a server is on the intranet it's presumed to be safe (itself a different problem), if a server self-identifies as being OK for Chrome the user gets a secured sandboxed environment. But on the Internet, where users will go, if a server doesn't self-identify as preferring Chrome the user is browsing a site with a browser that's known to be insecure. So by enabling users to browse in a secure environment when the server offers it, Google is actually enabling people to not update to a more secure browser.
It's a clever hack, but the premise is fatally flawed.
Help stamp out iliturcy.
Users don't know what a browser engine is. They don't even know what a browser is. They know that if they click on the big blue e, they can google the internet, and that's pretty much all they know.
The reason they're not switching to chrome is because even if they do manage to click and install it, they won't even realize that they have to click the chrome icon instead of the ie icon to browse the web. And even if they get as far as realizing that, they won't like chrome because it looks too different.
I'm surprised no one else has pointed this out. Look at what MS does to firefox. It seems that every time I log on to the Terminal Server at work and run Firefox there is a new damn MS plugin I have to disable and cannot be completely uninstalled. I called MS about this when it first started and they said "Oh no that's not us. Mozilla is installing it." Funny I know the firefox up date had not been run but Patch Tuesday had.
I guess my question to Microsoft is. What about the security problems you are installing without mt permission to software that you do not own like .NET framework and ActiveX controls? I use Firefox when I have to work from a Windows world to get about these security problems. Problems with .NET and ActiveX are very real and there are plenty of citations on the net to back this up.
Microsoft you were the first to piss in someone else's pond. Don't bitch when someone pisses in yours. At least Google really did FIX some of your problems. You should be grateful.
For those who don't already know, you can force a page to load with the Chrome Frame (if it's installed of course) even it if it doesn't have the tag embedded in the page by adding "cf:" in front of the address. e.g. cf:http://www.slashdot.org/