Chrome Stable Channel Update

Chrome has been updated to 31.0.1650.48 for Windows, Mac, Linux and Chrome Frame.
The update includes 25 security fixes.
More

 

Thank you for info. Patch Tuesday in full throttle

 

Yes, my life is on hold until complete.

 

Flash Player has also been updated to 11.9.900.152, which is included w/ this release.

 

AES-GCM support is finally here though no 256 bits variants:

2 things I also noticed: They prefer AES-GCM without Forward Secrecy over AES-CBC without Forward Secrecy, not sure if this is good. They also prefer RC4 over 128 bit AES-CBC which is not desirable IMO.

 

Chrome has been updated to 31.0.1650.57 for Windows, Mac, Linux and Chrome Frame.

Chrome Releases

 

Thanks, will be updating.

 

Pinkie Pie pocketed 50K for his troubles.
Must have been a major exploit.

 

Chrome has been updated to 31.0.1650.63 for Windows, Mac, Linux and Chrome Frame.
This update includes 15 security fixes.
Chrome Releases

 

The Chrome Team is excited to announce the promotion of Chrome 32 to the Stable channel. 32.0.1700.76 for Windows and Chrome Frame and 32.0.1700.77 for Mac and Linux. This release contains a number of fixes and improvements, including:
Tab indicators for sound, webcam and casting
A different look for Win8 Metro mode
Automatically blocking malware files
A number of new apps/extension APIs
Lots of under the hood changes for stability and performance
You can read more about these changes at the Chrome blog.

Flash Player has been updated to 12.0.0.41, which is included w/ this release.

Chrome Releases

 

Updating, thanks.

 

Sure thing.

I read under fixes and improvements... "Automatically blocking malware files".

Here's an article on that from a couple of months ago

Chrome browser will block malware downloads

 

Is it just me, or does Chrome scroll too quickly now? *Nevermind, corrected it in Microsoft Mouse and Keyboard Center with "Identify programs that don't scroll correctly..."

 

I was gonna say, this sounds like a poll question.
(Glad you got it fixed.)
Truth be told, Chrome always seems to get a kick in the seat of the pants immediately after an upgrade, though that's not what you were referring to.

 

Chrome profile is now corrupted on one of my computers.
Happened not long after updating.

 

What a relief, I thought I was only one. Mine got corrupted right after update. Uninstaled, deleted profiles folders and reintaled. In the morning it got corrupted again. Switched to Firefox for a while. I hope that they fix this.

Regards, hqsec

 

Yep, that's literally why I posted about it happening... to determine if it was just me or others wrestling with it.
And wrestling is a good word. I've lost bookmarks, extensions, then moved a Chrome Default folder (that contains all user data) over from another computer, then I got the corruption notice again, then rebuilt it a second time... or was it a third time?
I'm not sure but I think everything is going bad on reboot.
I'm with you. I hope they fix this.

It crossed my mind that it could be Windows Update related as well.
I installed all updates yesterday... did you?

Weird thing is, it's only puking on one of my computers.

 

Yes, I updated Windows 7 first and then updated Chrome. I will reimage and update Chrome to see if it works. Then I will update OS and see if that breaks Chrome.

Regards, hqsec

 

Here is an update. I restored OS image taken before yesterday's updates. I updated Chrome to v.32. I rebooted few times and open Chrome unsandboxed and sandboxed also (SBIE). The error did not occur. I updated OS (windows 7 32 bit - 3 updates + MSRT). Rebooted few times run Chrome - no error. After few minutes of browsing something interesting happened. My HIPS started to ask me questions about Chrome's setup.exe trying to run. I killed it and run Chrome unsandboxed. After a while questions reappear. I allowed the update to do it's thing. Here is a HIPS log, describing what happened during this second stage of update:

* log is only partial

It looks like update of Chrome is taking much longer and some update actions are postponed and run later, even after we would think that update has finished. If during this time Chrome would be run under SBIE it could break the update process and corruption could happen. I think that this happened to me the first time.

Right now, I have no problems with Chrome. I will monitor how it behaves and report back if I find out something new.

Regards, hqsec

 

Very interesting observation, and you may be on to something, except I don't allow Chrome to update in SBIE, and you're saying you think that updating inside SBIE might be what broke Chrome, right?
Or are you saying that Chrome trying to update while SBIE is running caused the corruption?

Yes, SBIE was throwing lots of error messages about setup.exe not being allowed to start.

Excellent plan.
Thanks for the troubleshooting.

 

Damn. I rebooted and Chrome puked again... corrupted Preferences.
I did use CrapCleaner prior to rebooting.
Perhaps I need to look at those settings.
So far, as luck would have it, this issue is only affecting one pc.
The unaffected one has the same OS. Puzzling, not to mention annoying.

 

The Google Chrome dialog I most recently received said:

Boy, they've got that right.

Now I'm looking at the new feature in Chrome that is automatically blocking malware files.

As the NetworkWorld article stated, this new Chrome functionality might trigger conflicts for users with other security software. With that in mind I have disabled real-time VIPRE protection, and I have not installed TrafficLight extension, which I believe uses BitDefender QuickScan. Still running MBAM real-time, and will disable that as well if need be in order to get to the bottom of this.

So far, this is a conversation with myself (pretty much) in order to document the issue in case someone else comes along and can use any of it. Or maybe one of you guys has it figured out!

 

If you were signed in and synced in Chrome you might have not lost anything.

 

Which antivirus engine does Chrome use?

 

I did not run update inside SBIE. But as it looks with this update it takes much longer to finish. Usually I would restart Chrome few times after update and nothing would happen after that. This time Google tries to do something (I guess finishing update or doing some maintenance after update) 10 to 15 minutes after update has been done. That means Google Chrome should run outside SBIE for let's say 30 minutes after update just to be sure that update has finished.

That was Crome trying to "finish update", but SBIE stopped it (process execution prevention).

Yes I've read about it. I don't like to be signed into Chrome. I have some privacy concerns about it.


Regards, hqsec