2 posts tagged with "encryption"

In an age of heightened privacy concerns, offering End-to-End Encryption (E2EE) is one of the most powerful ways to build trust with your users. It provides a mathematical guarantee that conversations are confidential and that not even your server can access the media streams.

While the technology is complex, implementing it doesn't have to be. This guide will walk you through the two E2EE models available in Plug-N-Meet and show you how to enable them with a simple API call.

In the world of secure communication, End-to-End Encryption (E2EE) is the gold standard. It ensures that only the participants in a conversation can decrypt and view the media streams, not even the server itself. At plugNmeet, we've implemented a robust E2EE model based on the WebRTC Insertable Streams API.

But "E2EE" isn't a single, one-size-fits-all solution. A critical question remains: where do the encryption keys come from, and who manages them?

plugNmeet offers two distinct models for managing E2EE keys, controlled by a simple setting: enabled_self_insert_encryption_key. Understanding the difference is key to choosing the right security posture for your application.