RTC Forums
November 23, 2024, 11:20:03 PM
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Home
Help
Login
Register
RTC Forums
>
Subscription
>
Support
>
SSL encryption and built-in encryption mutually exclusive?
Pages: [
1
]
« previous
next »
Print
Author
Topic: SSL encryption and built-in encryption mutually exclusive? (Read 4382 times)
dex
RTC Expired
Posts: 10
SSL encryption and built-in encryption mutually exclusive?
«
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
Re: SSL encryption and built-in encryption mutually exclusive?
«
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
« previous
next »
Jump to:
Please select a destination:
-----------------------------
Dashboard
-----------------------------
=> General
=> 3rd-Party
=> Quick Start
-----------------------------
Subscription
-----------------------------
=> Support
Loading...