Source-Nexus Gateway FAQ

This article is part of the Source-Nexus Gateway User Guide

GO: SOURCE-NEXUS GATEWAY WEB APP

General Information

What platforms does Source-Nexus Gateway work on?

Source-Nexus Gateway requires Google Chrome version 48. Chrome 50 is the last version available on macOS 10.6 and Windows. Some operating systems may no longer support Chrome, for future continued support you will need:

• macOS 10.9 or higher
• Windows 8.1 or higher
• Modern Linux support

Why doesn't Source-Nexus Gateway work on older systems?

Source-Nexus Gateway is dependent on security and feature updates by Google Chrome. Unfortunately, this means that as Google decides to stop supporting older systems, we need to update our systems also. This ensures the most secure experience for all users. It is Source Elements policy to take security seriously and this does mean that older systems may not remain supported.

What is the recommended method for staying up to date?

• Make sure you have Chrome automatic updates enabled under Chrome::Preferences.
• If you cannot upgrade your computer operating system to the minimum requirements for Chrome, you can also use modern Android tablets and phones, or the Chromebook

How much does it cost?

All accounts will be able to connect for audio-only sessions (up to 256kbps) for free. 

There is a paid option - the Source-Nexus Suite subscription (for screen sharing and access to the full Source-Nexus Suite, including the Source-Nexus I/O and Source-Nexus Review plugins, and the stand-alone Source-Nexus Router application).

Security

Is Source-Nexus Gateway encrypted?

Yes, Source-Nexus Gateway is encrypted E2E (end-to-end, full encryption).

Where is the encryption key for E2E encryption generated and stored?

Source-Nexus Gateway connections are encrypted using the Diffie-Hellmann key exchange method. The keys for the peer-to-peer SSL connection are generated by the peers and exchanged over the signaling protocol. The peers use a self signed certificate (asymmetric-key) based on RSA to exchange the symmetric keys they will use for the communication. The peers then use Diffie-Hellman to generate symmetric keys.

What is the encryption algorithm used for E2E encryption?

Streams are sent via DTLS (Datagram Transport Layer Security). DTLS is modeled after TLS.

Does the exchanged audio data go through the Source Elements server?

Yes. About 10% of the time, if there are firewall restrictions, it will pass through the relay servers. However, it is encrypted.

Is the exchanged audio data stored on the Source Elements server?

No, it never is.