3 ms·
Not sure if it's a Chrome update or macOS update as I did both at the same time, but since I updated to High Sierra I've started getting a lot of certificate er
by 7ewis 9y ago
Not sure if it's a Chrome update or macOS update as I did both at the same time, but since I updated to High Sierra I've started getting a lot of certificate errors in Chrome v59. I tried updating to the 60 Beta, but it is still occurring.
My company use a Cisco WSA to decrypt HTTPS traffic, and that cert is suddenly no longer trusted, and I seem to be unable to trust it. Despite it never being required to be trusted previously. Sites load fine in Safari though and off my corporate network.
- gruturo 9y agoSame issue at my job with McAfee proxies doing SSL interception. Newest Chrome complains because it doesn't use the CN field anymore and now demands SAN (Subject Alternate Name) fields be present instead - but the certs generated by our proxy lack them.
- pilif 9y agoThis change has caused so much pain in our internal network too. Not because of intercepting proxies, but because of a ton of certs signed by an I terns CA. I really wonder what kind of issue triggered them changing this and whether it was Wort the trouble. Stuff like this is why I can understand companies still being reluctant to allow browsers other than IE
- picofish 9y agoi think it was because the rfc that says which attributes of a cert must be checked by the browser was deprecated 15 years ago and everybody ignored the update (that says that the san attribute must be present)
- pronoiac 9y agoGah! Is it blocking self-signed certs? I'd seen that in Canary, but it didn't show up in what I thought was the corresponding Chrome. At work, we use a lot of self-signed certs, and we have a hosted product that generates them too; figuring out a plan for handling that is no fun. The best workaround we found was using another browser.