Prevent sniffing

[dex]

Hi,

What is the best strategy to protect from unwanted sniffing of data exchanged between RTC Client and Server, on the machine where client resides?

Does using SSL/TLS encryption with StreamSec plugin provides complete protection? Are there some settings I should be careful about?

Dex

[D.Tkalcec (RTC)]

Well ... you can not "prevent" sniffing, but as you can use encryption to prevent someone from reading your data in plain text in case they will read your communication.

If your data is not too sensitive and you are only using RTC remote functions, you can enable RTC encryption to have all the content sent and received using TRtcClientModule and TRtcServerModule components encrypted. See the "Encryption", "SecureKey" and "ForceEncryption" properties on TRtcServerModule and TRtcClientModule components for more info.

If you need more security, you should use SSL/TLS encryption. This is possible by using StreamSec Tools 2 components from StreamSec. Please contact StreamSec support directly for more information about their components and component usage.

Best Regards,
Danijel Tkalcec

[zsleo]

Is Eldos Secure Black Box still compatible with RTC?

Zane

[D.Tkalcec (RTC)]

From the RTC side, it is only a question of assigning a third-party plugin to the correct property on the RTC component (for which you need the RTC SDK, the correct plugin and third-party encryption components).

But ... to make things really work, you will also need to create and configure third-party encryption components correctly, which is something only the third-party component vendor can assist you with. This is why you should contact the respective third-party component vendor directly ("Eldos" - in your case) and ask *them* if they support the use of their components as plug-ins for the latest RealThinClient SDK version, not me.

Best Regards,
Danijel Tkalcec