Google-chrome – Force Chrome to Ignore a “weak ephemeral Diffie-Hellman public key”

Google disclaims a policy in the Chrome documentation. It essentially says Chrome doesn't gather any data besides what typing into the search field at google.com would provide Google with. While this does constitute a privacy risk, unless your IT blocks all access to Google, the argument doesn't hold water. (And is likely based on jumping to conclusions from skimming sensationalist headlines.)

Chrome and Chromium also collect additional data, the extent of which is mentioned in a blog post by the developers.

That said, I haven't tried watching Chrome with wireshark to verify what is actually sent to Google servers, so trust the above as much as you trust Google to keep their word to begin with.

It is nothing to worry about most of the time. Many of the web services and applications on the Internet in these days, are not 100% self sufficient and a web page, in today's Internet, is nothing but a combination of many different items from different locations. In order words, because the web is getting closer and closer to be an inseparable part of our social lives, it needs to incorporate many social items as well. Doing so, requires a website to try and retrieve data from different sources, which not all of them are using SSL protocol. This causes that green lock to go gray.

In a simpler language, when a webpage, which is using HTTPS(SSL), tries to incorporate or use some other items (Pictures, scripts, xml or css files, etc.) on other websites or servers, that do not use https, your green lock turns gray. Most of the time there is nothing to worry about, firstly because there is nothing much you can do, and secondly because this usually happens on non-so-highly-sensitive web pages, and you should only worry when it happens on you PayPal or bank account page.