Re:Zoom lied to users about end-to-end encryption for years,...
by MayeulC on Thursday November 12, 2020 @06:14AM
(#25068646)
I'd just like to point out that it's also very easy to do on most reverse proxies. Client cert, or even regular password protection.
Client certs are quite easy to setup. Create a CA cert, sign client certs with it, and allow only clients who have a cert signed by you.
Client cert on Nginx: https://fardog.io/blog/2017/12/30/client-side-certificate-au...
Bonus about client certs: https://drewdevault.com/2020/06/12/Can-we-talk-about-client-...
I have also used certificate authentication on TLS-terminating reverse proxies (e.g., this is easy to do with HAProxy) to do the same in other environments. You can pin the API's certificate on the client end in order to further reduce MITM risks.
If you don't want to supply a client certificate in your client application, Stunnel[1] is an acceptable wrapper that lets your clients remain TLS-unaware. You could use it for both ends of the tunnel, if you felt like it.
Either way, you end up with a secure tunnel through the internet to the proxy, at which point you're back inside private networks.
(Source: I build this kind of thing for a living.)
[0]: https://aws.amazon.com/blogs/compute/introducing-mutual-tls-...
[1]: https://www.stunnel.org/auth.html