Google has published a plan to stop supporting the algorithm SHA-1

The policy to remove support for the potentially insecure SHA-1 cryptographic hashing algorithm, taken by Google, found final features in a plan published on the company's security blog to stop supporting the SHA-1 algorithm. Information about this has been published before , but now, apparently, we will know the final dates and details of how Google sees the process of eliminating SHA-1 support.

Signs of weakness of the algorithm were first discovered more than 11 years ago, and Chrome will no longer trust websites with certificates that use the SHA-1 algorithm, and will display a notification about this.

Google plans to remove certificate support from SHA-1, starting with Chrome 56, which will be released by the end of January 2017. Website owners are advised to check their sites for using certificates with SHA-1, and contact their CA to replace those with certificates with SHA-256.

I will give an illustration from the last post on this topic:
')

Locally added certificates based on SHA-1 will continue their work until the release of Chrome 57, scheduled for March. For corporate users, the setting EnableSha1ForLocalAnchors is implemented, which allows you to bypass the restrictions and continue using SHA-1 in PKI.

Certificates with SHA-1, used for client authentication, and the EnableSha1ForLocalAnchors directive will be supported until January 1, 2019.