RTC Forums
April 23, 2024, 11:08:42 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: SSL encryption and built-in encryption mutually exclusive?  (Read 3309 times)
dex
RTC Expired
*
Posts: 10


« on: August 18, 2016, 02:22:28 PM »

Hi,

I read excellently written article "Strong Encryption with RTC remote functions". One question though needs clarification. In a setup where RTC remote functions are used with built-in encryption, and then SSL encryption is added via plugins, what is the final result? Does SSL somehow deactivates built-in encryption functionality, or the final message is technically encrypted twice?

Thanks!
Dex
Logged
D.Tkalcec (RTC)
Administrator
*****
Posts: 1881


« Reply #1 on: August 18, 2016, 03:51:19 PM »

The encryption functionality provided by TRtcClientModule and TRtcServerModule components is NOT related to SSL/TLS encryption available for TRtcHttpClient and TRtcHttpServer components. Adding SSL/TLS encryption to a TRtcHttpClient/TRtcHttpServer component does NOT deactivate RTC encryption set up on the TRtcClientModule/TRtcServerModule components. So .... if you enable RTC encryption on TRtcClientModule and TRtcServerModule components and use SSL/TLS encryption with TRtcHttpClient and TRtcHttpServer components, your data will be encrypted twice, using two entirely different encryption mechanisms.

Best Regards,
Danijel Tkalcec
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.021 seconds with 16 queries.