Chrome 56 will mark HTTP pages with password fields as non-secure
Posted by Emily Schechter, Chrome Security Team [Updated on 12/5/16 with instructions for developers] Developers : Read more about how to ...
Visit security.googleblog.com → On Hacker News Mar 2016 – Feb 2026
Security & Privacy 54Web & Frontend 10Software Engineering 10Networking & Internet 9Open Source 6Hardware & Electronics 6
Posted by Emily Schechter, Chrome Security Team [Updated on 12/5/16 with instructions for developers] Developers : Read more about how to ...
Posted by Emily Schechter, Chrome Security Product Manager For the past several years, we’ve moved toward a more secure web by strongly adv...
Posted by Jonathan Skelker, Product Manager It’s Halloween 🎃 and the last day of Cybersecurity Awareness Month 🔐, so we’re celebrating t...
Posted by Devon O’Brien, Ryan Sleevi, Andrew Whalley, Chrome Security This post is a broader announcement of plans already finalized on t...
One year from now, with the release of Chrome 154 in October 2026, we will change the default settings of Chrome to enable “Always Use Secure Connections”. This means Ch…
Posted by Chrome Root Program, Chrome Security Team Update (09/10/2024): In support of more closely aligning Chrome’s planned compliance ...
By: Arnar Birgisson and Diana K Smetters, Identity Ecosystems and Google Account Security and Safety teams Starting today , you can create a...
Posted by Patrick Nepper, Kiran C. Nair, Vasilii Sukhanov and Varun Khaneja, Chrome Team Today, we announced better password protection...
Posted by Stephen Röttger and Artur Janc, Information Security Engineers Three years ago, Spectre changed the way we think about security b...
Posted by Jay Brown, Sr. Technical Program Manager, Security For many years, we’ve worked to increase the use of encryption between our us...