3 ms·
Same 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 (Subje
by gruturo 9y ago
Same 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)