![]() ![]() ![]() ![]() You cannot visit host.domain right now because the website sent scrambled credentials that Google Chrome cannot process. Your information is still secure because Google Chrome stopped the connection before any data was exchanged. This may happen when an attacker is trying to pretend to be host.domain, or a Wi-Fi sign-in screen has interrupted the connection. When Google Chrome tried to connect to host.domain this time, the website sent back unusual and incorrect credentials. Host.domain normally uses encryption to protect your information. Where I would have normally expected an warning about a self-signed certificate, and an option to “ Proceed to test.DOMAIN”, I was instead faced with a very different warning: Then, I was recreating a local testing server self-signed TLS certificate, and Chrome was NOT happy. Having recently upgraded to MacOS Catalina, things seemed fine. Chrome on MacOS Catalina is especially persnickety when it comes to (self-signed) certificates, due in part, I believe, to Apple’s new certificate requirements for macOS 10.15 (Catalina) and iOS 13. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |