By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,812 Members | 1,324 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,812 IT Pros & Developers. It's quick & easy.

Serious Security Flaw in Google Chrome

P: n/a

Serious Security Flaw in Google Chrome:

http://www.readwriteweb.com/archives...gle_chrome.php

--
Guy Macon
<http://www.GuyMacon.com/>

Sep 6 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On 2008-09-06, John Bokma <jo**@castleamber.comwrote:
Guy Macon <http://www.GuyMacon.com/wrote:

>Serious Security Flaw in Google Chrome:

http://www.readwriteweb.com/archives...gle_chrome.php

"An attacker could easily trick users into launching an executable Java
file by combining a flaw in WebKit with a known Java bug and some smart
social engineering."

Old news [1], and certainly not serious. The most serious security flaw
are all those people *still* working with Windows with Administrator
rights. Some because they think they are "power users" (the correct term
is ignorant lusers), and some because an aforementioned "power user" has
configured their OS.
[1] I just explained to someone that when developing software, after some
time you freeze the code base. And if the release date is fixed (I am sure
that was the case here), it's just released, even if there is a very minor
security issue (which this is, anyone calling this serious is either
clueless, or trying to get more traffic)
Actually I think it was that "carpet bombing" issue that Microsoft were
having a bit of fun with in the press when it first appeared in Safari.

Apple had just rather sneakily installed Safari on a few million PCs by
bundling it into the small print of an iTunes update.

Soon after that when the "carpet bombing" problem was reported,
Microsoft responded by announcing serious-sounding warnings and
recommending people not to use Safari (which was brazen coming from
them, even for them).
Sep 6 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.