# mediasoup-demo with End-to-End encryption with WebRTC Insertable Streams **URL:** \ **Category:** Announcements\ **Created:** [March 29, 2021, 10:36am UTC](https://mediasoup.discourse.group/t/mediasoup-demo-with-end-to-end-encryption-with-webrtc-insertable-streams/2639 "2021-03-29T10:36:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [March 29, 2021, 10:36am UTC](https://mediasoup.discourse.group/t/mediasoup-demo-with-end-to-end-encryption-with-webrtc-insertable-streams/2639/1 "2021-03-29T10:36:24Z")
e2e (end-to-end) encryption added to mediasoup-demo app (by @vpalmisano): - [mediasoup demo](https://v3demo.mediasoup.org/?roomId=YOUR_ROOM_ID&info=true&e2eKey=YOUR_KEY) Just replace `YOUR_ROOM_ID` and `YOUR_KEY` with your own values and open the link in two Chrome/Canary tabs. If you remove `e2eKey` from the URL params in one of the tabs and reload it, you will just listen to and see garbage. Related issue in GH: [Support End-to-End Encryption with WebRTC Insertable Streams · Issue #383 · versatica/mediasoup · GitHub](https://github.com/versatica/mediasoup/issues/383) ---
**Author:** ![vpalmisano](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/vpalmisano/32/43_2.png) [@vpalmisano](https://mediasoup.discourse.group/u/vpalmisano)\ **Post date:** [March 29, 2021, 11:35am UTC](https://mediasoup.discourse.group/t/mediasoup-demo-with-end-to-end-encryption-with-webrtc-insertable-streams/2639/2 "2021-03-29T11:35:26Z")
It works on Google Chrome stable (89.0.4389.90) 😉 ---
**Author:** ![skp](https://avatars.discourse-cdn.com/v4/letter/s/87869e/32.png) [@skp](https://mediasoup.discourse.group/u/skp)\ **Post date:** [March 31, 2021, 10:07am UTC](https://mediasoup.discourse.group/t/mediasoup-demo-with-end-to-end-encryption-with-webrtc-insertable-streams/2639/3 "2021-03-31T10:07:48Z")
Great work @vpalmisano. The demo is working like a charm in my Google Chrome stable (89.0.4389.90). I am running chrome on Ubuntu 20.04 LTS. While trying the demo for a couple of times initially, the demo crashed my chrome with error code as SIGSEGV. It only happened initially for 3 to 4 times and after that it started working fine. Can there be a logic for such a behavior of my chrome? ---
**Author:** ![vpalmisano](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/vpalmisano/32/43_2.png) [@vpalmisano](https://mediasoup.discourse.group/u/vpalmisano)\ **Post date:** [March 31, 2021, 10:11am UTC](https://mediasoup.discourse.group/t/mediasoup-demo-with-end-to-end-encryption-with-webrtc-insertable-streams/2639/4 "2021-03-31T10:11:41Z")
Maybe related to Chrome. Try enabling logs from command line and send a bug report to [https://bugs.chromium.org/](https://bugs.chromium.org/) ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [March 31, 2021, 10:25am UTC](https://mediasoup.discourse.group/t/mediasoup-demo-with-end-to-end-encryption-with-webrtc-insertable-streams/2639/5 "2021-03-31T10:25:17Z")
Yes, please, mediasoup contributors are not responsible of Chrome/libwebrtc bugs. Do not do bypass. Please, report to Chrome or libwebrtc projects. ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/mediasoup/original/2X/b/b318c4d3397e65af9535f79c605b80b9ceb066c8.png) [@system](https://mediasoup.discourse.group/u/system)\ **Post date:** [March 31, 2021, 10:37am UTC](https://mediasoup.discourse.group/t/mediasoup-demo-with-end-to-end-encryption-with-webrtc-insertable-streams/2639/6 "2021-03-31T10:37:13Z")
This topic was automatically closed after 2 days. New replies are no longer allowed.