Carpetbomb bug tarnishes Google Chrome
Shiny new vulnerabilities winkled out already
Google Chrome isn't officially out yet, but security researchers have already picked the browser apart to discover a security vulnerability.
The WebKit engine used inside Chrome leaves it vulnerable to the infamous Safari carpetbombing flaw, security researcher Aviv Raff warns. The flaw stems from a combination of a vulnerability in Apple Safari WebKit and a Java security bug, security blogger Ryan Naraine reports.
As a result Windows users of the beta software might be tricked into downloading malicious files onto their desktop. Raff has published a harmless proof-of-concept exploit in order to illustrate his concerns.
Apple patched the vulnerability with Safari v3.1.2, but the underlying software behind Chrome is based on older code, hence the vulnerability.
Security watchers warn further vulnerabilities are bound to arise. Against this many are praising the speed and built-in security features of the browser. Chrome features built-in sandboxing for each tab, anti-phishing technology and a privacy (ie smut-surfing) mode. ®
Re: Why would Google push their own browser?
Actually, the answer is much simpler that. Since Google is dependent on Microsoft, Mozilla, Opera and the like for the means to push their ads, it only makes sense for them to eliminate the middle man as much as possible. They have likely incorporated lots of code for ad-serving that won't be bypassed by helpful plugins like Adblock.
If the answer doesn't have something to do with world domination, then we're not talking about Google.
No reason to use the Google-approved browser when we already have good choices. I've been using Firefox since the early Mozilla betas and certainly haven't been disappointed in a long time. I don't really care about how well it renders some really screwed up smiley face test either, but I do want to block ads as I see fit and the addons like LiveHTTPHeaders and features like the Password Manager make the browser a better user experience than I can get with any of the others.
Looking at my website in Chrome, I find that everything now hugs the left margin even though the code says to centre it all. It simply can't interpret layout code.
This is a really basic flaw. I know its a Beta but this is a Bad Beta.
Re:not such a big problem
The minimal option has also a minimal control about cookies.
'Restrict how third parties cookie can be used" - what is that? seems to still accept all of them.
Now, I set my default search to scroogle (url http://www.scroogle.org/cgi-bin/nbbw.cgi?Gw=%s) only browse sites in my LAN and still the infamous google ID cookie appears every time you start the browser. It does not matter if you delete it , it comes back after while.