2 ms·
This kind of thinking is why PGP never took off. Yes, your ISP could hack the binaries, break the HTTPS trust model somehow, and alter what you download, but p
by jandrese 7y ago
This kind of thinking is why PGP never took off.
Yes, your ISP could hack the binaries, break the HTTPS trust model somehow, and alter what you download, but practically speaking that isn't going to happen. Trying to build your system to defeat an adversary who has that kind of power ends up making it too cumbersome for the 99.999% use case.
What I don't understand is why the server needs to decrypt the traffic at all. Why not just have it rebroadcast the encrypted streams? The endpoints could exchange crypto keys with public key crypto and to the video server it would just be a bunch of bytes. Clients would turn on and off video streams from different clients based on network conditions and how much screen real-estate they have. Audio could even be encoded on a different channel so it could always be forwarded even if the video is not.
- ComodoHacker 7y ago>What I don't understand is why the server needs to decrypt the traffic at all In short, to make it scale for many (tens to hundreds) participants. Clever techniques like Simulcast[0] and SVC[1] allow that, but routing server must support it to meet different requirements of individual participants. 0. https://webrtchacks.com/sfu-simulcast/ https://webrtchacks.com/sfu-simulcast/ 1. https://webrtchacks.com/chrome-vp9-svc/ https://webrtchacks.com/chrome-vp9-svc/
- topranks 7y agoWith media streams the provider typically wants to be able to recode the data to lower quality to fit the bandwidth available to clients with lower bandwidth / congestion etc. There are ways around this but they are quite complex and place additional CPU overhead on each sender. Always Tradeoffs.