Chrome Stable Channel Update

Nope, not on my installations.

 

I got it in the latest update for Chromium on Arch linux, but not yet in Chrome for Windows (version numbers match).

 

Latest: 51.0.2704.79
http://googlechromereleases.blogspot.ca/2016/06/stable-channel-update.html

 

Version 51.0.2704.79 m (64-bit)

Google Chrome is up to date.

 

This update includes 15 security fixes.

 

One of the two Google Update Services on one of my machines once again reset itself to Automatic startup type, meaning Chrome had already updated itself when I went to perform the update manually. My best guess is that Windows Update is making this change, yet how odd that it is happening on just one of two 7x64 computers. I must remember after next round of Bork updates to recheck Services to see if Google Update was changed.

 

Wow, Chrome is nearly ready for CFI, https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-integrity

Privacy/security improvements are

1. Major improvement of password manager (new Credential Management API)
2. Same site cookie attribute (https://tools.ietf.org/html/draft-west-first-party-cookies-07) to reduce risk of data leakage.
3. Referrer granularity improved (https://w3c.github.io/webappsec-referrer-policy/)
4. Extension related code refined (probably reason for the extensions related bounties)

 

The stable channel has been updated to 51.0.2704.84 for Windows, Mac, and Linux.
http://googlechromereleases.blogspot.com/2016/06/stable-channel-update_6.html

 

Version 51.0.2704.84 m (64-bit)

Google Chrome is up to date.

 

according to ggogle.co.uk

however chrome says "Google Chrome is up to date."

 

Maybe you're using an adblocker or any program that manipulates Chrome's identification of its version to prevent tracking. I know Adguard and uBlock Origin have this option.

 

I left a spoof of chrome 42 headers in by accident, so yeah found the cause now.

 

Is it possible to turn off the DNS callouts made by Chrome to clients1.google.com and clients2.google.com (I think that's what they are)... they're never ending!

 

Using this switch: --disable-async-dns
Use this to clear DNS cache: chrome://net-internals/#dns

 

Thanks for the advice! I will give it a shot

EDIT: Thanks once again. I also added --disable-background-networking and --dns-prefetch-disable! Silence! Now to get out of Shadow Mode and try this for real.

 

async-dns has nothing to do with dns prefetching, disabling that you just hurt your performance.

 

Version 51.0.2704.103 m (64-bit)

Google Chrome is up to date.

 

Version 51.0.2704.103 m (64-bit)

Google Chrome is up to date.

 

I don't mean to disrespect you Dragon1952, but why you always post the same message here after another member has already warned us about an update?

It's clearly just spam.

----

Changelog for 51.0.2704.103:

http://googlechromereleases.blogspot.com/2016/06/stable-channel-update_16.html

 

At least he's on topic, which is more than can be said for a great many posts recently on this UPDATES thread.

 

I ignored him right after that post so i won't be hearing from him again.

 

He always post the same message everytime an update is released and has already been posted here by another member. What's the point of it?

If other members followed his example this thread would be full of:

Version xx.x.xxxx.xxx m (64-bit)

Google Chrome is up to date.

I don't know about you but if you find this useful to the thread then facepalm. Repeating other users with the same information is just spam.

And btw, just because i said that, he added me to his ignore list when i clearly said i didn't want to disrespect him, i just wanted to know why he does such thing.

That just shows how mature he is.

 

It may be a repeated post, but as mentioned before, at least it pertains to the topic.

To be honest, I really don't see it being a big deal.