2 ms·

I worked for a place that did something similar, they were running a server on their local machines listening to https://localhost.company.com:someport https://

I worked for a place that did something similar, they were running a server on their local machines listening to https://localhost.company.com:someport https://localhost.company.com:someport (resolving to 127.0.0.1) so their javascript frontend hosted at example.com could communicate with their local machine. It was set up so the server would only respond to requests originating from company.com. They distributed the private key for the certificate localhost.company.com which was trusted by all browsers. What kind of risk is there to having the private key to localhost.company.com?

vbezhenar 8y ago
Well, CA forbid that kind of usage, so if they found out, they'd revoke that certificate, that would be the major concern for me. Other than that, obvious attack is to extract private key from your application, launch fake server and forge DNS responses for some poor guy (for example if he's using some untrusted WiFi). So his requests would be redirected into that fake server instead of localhost application.