Google Pushes Out Chrome Fix For Serious Security Hole
Google released an update to its web browser, Chrome, last night in order to fix a high-risk security hole. Chrome updates on its own, meaning that the only thing users should need to do is restart their browser to ensure they’re running the latest and greatest (assuming their browser was running and has downloaded the update). [Google Chrome Releases via CNET]
- Next Post: ListenToYouTube Rips Audio From YouTube Vidoes To MP3 »
- « Previous Post: Run The OLPC OS From A Thumb Drive
Comments (AU Comments | US Comments)
I'm surprised that this wasn't exploited at that hacker contest last month. Maybe it was?
cha0tic
I had to update mine manually under About Google Chrome as it didn't update automatically for me.
@Shashank Agarwal: Click the tool-icon and choose "about" - at the bottom of the about-window it will say if a new version is available.
Smukkekim
@Shashank Agarwal: Click the tool-icon and choose "about" - at the bottom of the about-window it will say if a new version is available.
Smukkekim
@Shashank Agarwal: Click the tool-icon and choose "about" - at the bottom of the about-window it will say if a new version is available.
Smukkekim
According to File Hippo, it's not in beta anymore.
Unless I'm thinking of Google Chrome 2
According to File Hippo, it's not in beta anymore.
Unless I'm thinking of Google Chrome 2
According to File Hippo, it's not in beta anymore.
Unless I'm thinking of Google Chrome 2
How do you tell if it has been updated?
Shashank Agarwal
How do you tell if it has been updated?
Shashank Agarwal
How do you tell if it has been updated?
Shashank Agarwal
I wonder if this flaw applies to Chrome 2. beta
gpzbc
I wonder if this flaw applies to Chrome 2. beta
gpzbc
I wonder if this flaw applies to Chrome 2. beta
gpzbc
@granbabydigi: Annoyingly it didn't update automatically for me either :(
littlemissellie
Mine did not update either, but note that it never has in the past either. 1.0.154.48 to 1.0.154.59 for those keeping track.
While we're discussing it, does anybody else get some janky things going on when you try to comment with Chrome here?
Ben Hull
Mine did not update either, but note that it never has in the past either. 1.0.154.48 to 1.0.154.59 for those keeping track.
While we're discussing it, does anybody else get some janky things going on when you try to comment with Chrome here?
Ben Hull
@algarx: So much for stable. :)
paintbox
[googlechromereleases.blogspot.com]
read here. it only affects stable version users, and updates to 1.0.154.59.
But the best part was that this bug is Internet Explorer's fault :D And it could affect you only if you were using Internet Explorer... lool
algarx
This only affects versions 1.0.154.55 and earlier. If your running the Beta version (Chrome 2), you are not vulnerable.
NorineParrot