Errors on secured GstRtspServer with prococols” GST_RTSP_LOWER_TRANS_TCP
sebastian at centricular.com
Wed Apr 20 06:19:51 UTC 2016
On Di, 2016-04-19 at 16:58 +0200, marc lievens wrote:
> Hi Sebastian,
> Sorry for the many questions, but I really new in this security matter.
> if I understand correctly, then since in server the certificate is specified and since also profile GST_RTSP_PROFILE_SAVP or GST_RTSP_PROFILE_SAVPF is set
> When used via tcp rtsp message and video is secured
> When used via Udp the rtsp message and video is secured
> But when I change profile to GST_RTSP_PROFILE_AVP or GST_RTSP_PROFILE_AVPF
> When used via tcp rtsp message and video is secured sine certificate is still specified
> When used via Udp the rtsp message are and video is not secured
> Is there some more info about this issue in gstreamer or some examples
> I will also take a more in depth look at the rtc5124 specifications and ,.....
I don't think any RFC explicitly says this. That's just how it works.
RTP is unencrypted, SRTP is encrypted. TLS is (usually) encrypted,
sending unencrypted RTP via TLS gives you protection.
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 949 bytes
Desc: This is a digitally signed message part
More information about the gstreamer-devel