I've read that a common way for servers to handle the SSL certificate is that the private key is not encrypted.
Now, a many web servers are getting hacked each day. Assumed that the private key is stored without encryption, the attackers could get the private key for the server's SSL certificate.
Some administrators may (at some point) realize that they got hacked, and some of those may revoke their certificate. Others may not even realize that their server and its SSL certificate got compromised.
Of course, if someone hacks a server, the attacker can manipulate the website. But this probably can get detected quite easily.
However, stealing and using the certificate including the private key is much more subtle and could be used with DNS spoofing for a man in the middle attack. Neither the user nor the server's administrator would detect any issues, but the whole traffic can be read by the attacker.
How is this handled in practice?
Do we have to assume that a server didn't get hacked to trust an SSL connection with a server?