Contents
How to get rid of obsolete cryptography warning?
To remove the “obsolete cryptography” warning, you’ll need to use “modern cryptography” which is defined as: This has nothing to do with a certificate. There is a special “outdated security settings” warning when a certificate uses weak signature algorithm, but this is about authentication, not about encryption.
Why does chrome say we are using IIs certificate?
When browsing over HTTPS to the website and inspecting the icon using chrome, we get a message “Your connection is encrypted with obsolete cryptography”. How do I configure IIS so that Chrome stops displaying this message, also need to balance the need to support IE>=8.
Is the RSA key exchange in Google Chrome obsolete?
Since the protocol version is good and AES_128-GCM is certainly not obsolete the remaining possibility is that something is wrong with the RSA key exchange. I’m not sure what google chrome understands as obsolete, but just the fact that key exchange is performed using RSA is not particularly good.
When is SHA-1 certificate deprecated in chrome?
SHA-1 is deprecated in Chrome at the start of 2015. Certificates expiring in 2016 will be marked as “secure, but with minor errors”. Certificates expiring in 2017 are later will be treated as “affirmatively insecure”.
What does version 41 of Google Chrome mean?
When you upgrade the Google Chrome browser to version 41 or later, you may see various warning messages such as, “The identity of this website has not been verified,” “Your connection to is not encrypted,” or other visual indications that the https connection is not secure.
What kind of certificate do I need for Google Chrome?
Those indications can appear when your SSL certificate uses a SHA-1 signature (most SSL certificates issued before 2015 use SHA-1). To fix the problem of browser security warnings you must get your SSL certificate re-keyed for SHA-2. If you don’t see those warnings in Chrome and you purchased your certificate recently, it may already be SHA-2.