Re:Certificates for localhost
by hamandcheese on Wednesday June 20, 2018 @07:23PM
(#17360795)
Only if you ship the private key with your app. Otherwise the MITM will fail certificate validation.
How would you run a local HTTPS server without the private key?
They get one private key per user, and send it to the client's device.
Re:Certificates for localhost
by BillinghamJ on Saturday June 23, 2018 @08:19AM
(#17380922)
The private key is generated on the client side, and signed by the certificate. Plex has an intermediate which they control to issue these. It would not pass normal validation processes.
Which "compromises" the key, according to current Certificate Authorities policies. Once again the problem boils down to CAs being the sole "anchors of trust" in the current certificate system.
Then they could have their server tunnel ACME challenges to the device, so the private key never leaves the device, but can still be signed.
Oh, indeed.
> By introducing a domain name instead of an IP address, you make it possible for an attacker to Man in the Middle (MitM) the DNS lookup and inject a response that points to a different IP address. The attacker can then pretend to be the local app and send fake responses back to the web app, which may compromise your account on the web app side, depending on how it is designed.