Chrome Stable Channel Update

Material Design is now the default for chrome://settings/
But there is (still) a flag (see chrome://flags) to disable it.

 

chrome://history/ was already Material. The new settings yep, was introduced in this newer version as mentioned on the release notes

 

TY for the heads up. This update includes 30 security fixes!

 

Thanks!

And thanks!

 

Did is fix this one?

https://thehackernews.com/2017/05/chrome-windows-password-hacking.html

 

My guess is you're asking a question that you know the answer to. Why is that?

 

Ok, thanks.
I rarely look at the history so i wasn't aware of it.

 

I do not, thus why I am asking.

 

I just updated to chrome 59 and afterwards when I try to update Avira Browser Safety it says it's corrupted and it won't repair it when I try, so I have no choice but to uninstall it, then when I go to the web store it's not there anymore! WTH google, that's my all time favorite extension!

 

Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$7500][722756] High CVE-2017-5070: Type confusion in V8. Reported by Zhao Qixun(@S0rryMybad) of Qihoo 360 Vulcan Team on 2017-05-16
[$3000][715582] High CVE-2017-5071: Out of bounds read in V8. Reported by Choongwoo Han on 2017-04-26
[$3000][709417] High CVE-2017-5072: Address spoofing in Omnibox. Reported by Rayyan Bijoora on 2017-04-07
[$2000][716474] High CVE-2017-5073: Use after free in print preview. Reported by Khalil Zhani on 2017-04-28
[$1000][700040] High CVE-2017-5074: Use after free in Apps Bluetooth. Reported by anonymous on 2017-03-09
[$2000][678776] Medium CVE-2017-5075: Information leak in CSP reporting. Reported by Emmanuel Gil Peyrot on 2017-01-05
[$1000][722639] Medium CVE-2017-5086: Address spoofing in Omnibox. Reported by Rayyan Bijoora on 2017-05-16
[$1000][719199] Medium CVE-2017-5076: Address spoofing in Omnibox. Reported by Samuel Erb on 2017-05-06
[$1000][716311] Medium CVE-2017-5077: Heap buffer overflow in Skia. Reported by Sweetchip on 2017-04-28
[$1000][711020] Medium CVE-2017-5078: Possible command injection in mailto handling. Reported by Jose Carlos Exposito Bueno on 2017-04-12
[$500][713686] Medium CVE-2017-5079: UI spoofing in Blink. Reported by Khalil Zhani on 2017-04-20
[$500][708819] Medium CVE-2017-5080: Use after free in credit card autofill. Reported by Khalil Zhani on 2017-04-05
[$N/A][672008] Medium CVE-2017-5081: Extension verification bypass. Reported by Andrey Kovalev (@L1kvID) Yandex Security Team on 2016-12-07
[$N/A][721579] Low CVE-2017-5082: Insufficient hardening in credit card editor. Reported by Nightwatch Cybersecurity Research on 2017-05-11
[$N/A][714849] Low CVE-2017-5083: UI spoofing in Blink. Reported by Khalil Zhani on 2017-04-24
[$N/A][692378] Low CVE-2017-5085: Inappropriate javascript execution on WebUI pages. Reported by Zhiyang Zeng of Tencent security platform department on 2017-02-15
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
As usual, our ongoing internal security work was responsible for a wide range of fixes:
[729639] Various fixes from internal audits, fuzzing and other initiatives
https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html

 

This issue can also be seen with the Norton Toolbar: ("this extension may have been corrupted" error message)
(Edit: Norton has released an updated version of the Norton Security Toolbar: #1169)
You can try to change the following flag to "Bootstrap":
chrome://flags/#extension-content-verification
Restart the browser and see if it can be repaired now. If not, then i guess you'll have to wait for an updated extension or chrome-version

-------------

Yes, it has been fixed:

 

I never heard of Avira Browser Safety so I tried searching the Chrome Web Store for it but the closest thing I could find was Avira Safe Shopping. I read the reviews and something felt off. I googled each reviewer's name + Avira and three out of four works for Avira.

I found a working link to Avira Browser Safety on an employee's Google Plus profile.

https://chrome.google.com/webstore/detail/avira-browser-safety/flliilndjeohchalpbbcdekjklbdgfkk

 

Thank you mood. Much appreciated.

 

It seems that last update resolved a problem with click-to-play setting for Flash. Though I didn't miss anything while not using it

 

If you have version 58 or below you should be able to see ABS in the chrome store cause it said it was updated today, but after updating to chrome 59 it says it's been disabled which is strange...I can see it on my son's computer since his hasn't been updated but my pc and the family pc has been updated to v59 and I can no longer see it

Whoever uses ABS, after updating to chrome 59, try updating extensions (developer mode ticked) and it will say it's corrupted


EDIT: Thanks for the link but here's what happens when I installed it, and repairing doesn't work

 

Good heads up, mood. TY.
Required manual updating File Type Policies on my machines after upgrading to 59.0.3071.86 , i.e. it was still on v8 after upgrading Chrome. Not a lot of people will know enough to manually update.

 

And thank you, Trooper for asking. I apologize that I misunderstood your motive. My bad.

 

Norton released an update to their toolbar which fixes their issue.

https://www.wilderssecurity.com/threads/the-symantec-norton-thread.372604/page-33#post-2682583

 

No problem man. Cheers.

 

Thanks

A new version of the extension has been published today.
https://chrome.google.com/webstore/detail/avira-browser-safety/flliilndjeohchalpbbcdekjklbdgfkk
Avira Browser Safety - v2.4.2.1650 (7 Jun 2017)

 

http://www.makeuseof.com/tag/avira-browser-safety-compare-web-protection/

 

It looks like it's independent from the browser update. I don't have an installation on Chrome v58 anymore to check for sure, but the latest Vivaldi stable, which is using Chromium 58, and an installation of Chromium 58 already updated File Type Policies to v11.

 

Yes, before i have upgraded Chrome to v59, File Type Policies was already at v11.

 

Great news! Thanks