Short two-person transcript from a YouTube video by Tsahi Levent-Levi discussing whether TURN/TLS is more secure than TURN/TCP for WebRTC. Speakers agree that WebRTC media/data are already encrypted, so TURN/TLS does not materially increase security (it creates redundant encryption). The practical benefit of TURN/TLS is better traversal of restrictive ("stupid") firewalls; recommendation: offer both TURN/TCP and TURN/TLS so ICE can prefer TURN/TCP when available and fall back to TURN/TLS when needed.
Chapters
Is turn TLS more secure than turn tcp? Whoever TC calls? Because we all know TLS has encryption. TCP isn't encrypted.
Yes, but I mean there is no difference in this. For security concerns, we are doing turn TLS and encrypting the already encrypted WebRC stuff, which is double encryption, which in general is something you would like to avoid. But the advantage of using turn TLS over turn TCP is that more stupid firewalls allow you to pass through turn TLS.
Okay, so WebRTC media and data is already encrypted, so we don't really care from a security perspective if we use.
TCP or.
TP tls. In this case, the only reason for us to use turn TLS is because it might pass or traverse firewalls a bit better or in a bit more situations than TurntCP.
Yes, so you should always be offering both alternatives TurntCP and turn TLS. Lepropicy will prefer TurntCP because of ICE priorities, which means whenever it works, you get that you don't do the double encryption when it's not necessary and you get turn TLS when it's required.
