squarewave said:
In theory I suppose a government could force people to use a browser with their own CA cert (maybe intercept a download of chrome or whatever browser and substitute their own version with their CA in it). Then they could change DNS for sites and use their own certs.
Otherwise, browsers would just remove a "sloppy" CA and then it wouldn't work.
There are also the cases of CA's gving out certs without checking who they are going to. A few years ago, a researcher obtained google.com certs from Symantec, fi.
And then there are the cases of badly configured servers. Ones that still accept older versions of SSL that can be decrypted on-the-fly or offline.
You could also install your own root cert on a device you'd like to monitor. With today's proliferation of DIY USB attack kits, it's a jiffy if you have physical access to the machine. Even if you haven't got access, you'd only need to visit a Starbucks or such where the victim uses the procided Wifi to get in and do your thing. Hotel/airport wifi comes to mind.
Besides, there's a lot of other trickery too. It's like NAT traversal. Not easy, no commercial products around, afaik, but fi Skype has been doing it for years, circumventing firewalls. And there are some github projects to DIY. Of course, NAT traversal isn't encryption, it's just a way into your (home) network.
It's usually not one thing, but a number of exploits to get into a system...
And SOHO routers are often the starting point.
For those interested, here's a Network World article about it:
https://www.networkworld.com/article/2163739/what-s-lurking-in-your-network--find-out-by-decrypting-ssl.html
And Moxie Marlinspike's take on the subject:
https://moxie.org/blog/ssl-and-the-future-of-authenticity/
It's not as if PKI/SSL an sich are so bad, security-wise, it's just that we, the user, aren't really informed. And that opens many avenues to attack.