Diffie–Hellman[0] is pretty cheap, you do it every time you visit a site with SSL enabled. Having the meeting leader do it 200 times to pass around a shared key

Diffie–Hellman[0] is pretty cheap, you do it every time you visit a site with SSL enabled. Having the meeting leader do it 200 times to pass around a shared key generated on the client would be e2e and have minimal if any performance impact. There is probably a cleverer way to do it that I'm not aware of as well. Edit: One issue is the client can run out of entropy but I think that would only happen on modern operating systems if you had hundreds of thousands of clients to negotiate with. [0]https://en.m.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange https://en.m.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_e...