License agreement for Chrome has ugly aspects

With all the publicity of Google’s new Chrome browser, there are a few issues that are turning up.

There seems to be a security vulnerability with it, as outlined in Infoworld. It can be serious especially if you’re not all that computer savvy.

“… serious vulnerability could result in Chrome users downloading malicious code. The problem is due, in part, to the fact that Google uses an older version of WebKit, the open-source browser technology also used in Apple’s Safari browser, that includes the vulnerability.”

OK. Chrome is in beta, meaning it’s still being fixed. Allegedly.

But there’s something even more serious. The End User License Agreement (EULA), which is all that fine print you usually ignore when you download something, has some really ugly problems.

An example is with the rights to anything you pass through that browser: “By submitting, posting or displaying the content you give Google a
perpetual, irrevocable, worldwide, royalty-free, and non-exclusive
license to reproduce, adapt, modify, translate, publish, publicly
perform, publicly display and distribute any content which you submit,
post or display on or through, the services.”

Also, Google has the right to update Chrome automatically, whether you want it done or not. Shades of America Online, and more recently Windows.

From the EULA: “You agree to receive such updates (and permit Google to deliver these to you) as part of your use of the services.”

Ugh.

If this EULA is a problem with you, then you just may want to stick with Firefox. Or Opera. Or Konqueror. Or Lynx. Maybe even (I must be kidding here) Internet Explorer.

I’ll still check it out when it’s available in Linux, but the EULA makes me nervous.

(My sources here: Slashdot and CNet.

(There probably will be more to come on this matter.)

This entry was posted in Uncategorized and tagged , , , , . Bookmark the permalink.