SHA1 is broken, and SSL certificates using SHA1 are not secure anymore (it's now been a long time that Chrome showed this to you - now it blocks NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM).Īnother likely cause is that your SSL-certificate expiredĪlso, you should disable backwards-compatiblity with SSL2 & SS元 ( Poodle Attack). If this happens, the most-likely cause is that your (or the website's) SSL-certificate uses SHA1. When that day comes, a website that still uses the function Warnings until Chrome completely stops supporting SHA-1 on Januaryġst, 2017. Just in case, Google plans to continue issuing Mountain View says it's hoping you don't ever encounter the message,īecause Certificate Authorities are required to stop issuing SHA-1Ĭertificates in 2016. It doesn't go away by restarting the browser, and it's not a bug. This is an increase in security enforcement. This happens when you update from Chrome 55 to Chrome 56 (.87).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |