Re:Sennheiser Headset Software Could Allow Man-In-the-Middle...
by kilburn on Wednesday November 28, 2018 @09:21AM
(#18551609)
If you want an arbitrary (thus https based) website to be able to communicate with a localhost server using websockets you are forced to use https on the localhost server. This is because the browser won't connect to non-secure websockets from an https website, even if the websocket is to localhost.
The actual right thing to do is to generate a private key and certificate (for a specific, public name you point to 127.0.0.1) during the software installation and add the latter to the trusted store. Now you don't have this vulnerability because each computer has a different trusted certificate with a different key, so a random attacker cannot just use the key they got to spy on other users.
Re:Sennheiser Headset Software Could Allow Man-In-the-Middle...
by plopz on Wednesday November 28, 2018 @09:14AM
(#18551554)
Blizzard ended up doing it the right way.
The Right Thing (TM) is to not do HTTPS, a modern web browser is supposed to conclude that ::1 and 127.0.0.1 are secure without HTTPS since there is no possibility of a "man in the middle" of your own computer's loopback.