If I am shown ERR_CERT_COMMON_NAME_INVALID, and I can see that the domains do not match (cert for *.example.com but I am visiting https://foobar.com), do I understand correctly that someone packet sniffing will still see encrypted traffic?
I'm trying to make sure I understand the threat of accepting these incorrect SSL certs. As I see it, it would be possible that a MITM is reading the traffic (decrypt it, then encrypt it correctly to pass it to the https site?) But unlike http it would still be encrypted traffic to someone "outside" - yes?
It's been a long sleepless night so forgive the stupidity.