Quantcast
Viewing all articles
Browse latest Browse all 10022

Re: Importing SSL Certificates into a different Keystore file

Hi Mr. Izak,

 

That's fine as what it's essentially stating is the name of the owner of the URL isn't within the certificate file. Of which, since Chrome is unable to verify the owner, it's basically telling you that someone could be spoofing their website to look like a valid website, but in fact it's not. Thus, that's the warning Chrome gives you:

 

This means that the security credentials the server presented could have been forged, and the server may not be the server you expected (you may be communicating with an attack).

 

Since this is an internal website, there's nothing to worry about with that warning. Especially considering that, in your next screenshot, it tells you that your connection is encrypted. Thus, SSL is working as expected within Chrome, it's just unable to verify the appropriate owner of the website.

 

Please let me know if you have any other questions/concerns with this. Thanks in advance,

 

-Victor


Viewing all articles
Browse latest Browse all 10022

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>