> On Mar 12, 2021, at 3:01 AM, Kommoju, Sekhar via live-devel
> wrote:
>
> Background: As per your comment, I’ve modified the testRTSPClient to call the
> function “useTLS()” on “RTSPClient” before sending the first RTSP command,
> but unfortunately I was getting a “Bad Request” error respon
> Does this encrypt only the RTSP part of the conversation? Is the video still
> in the clear?
Only the RTSP connection is encrypted. RTP/UDP packets are unaffected. There
is currently no support for SRTP. And, once again, this change is only for
our client implementation of RTSP.
>
I can diff the code once it downloads but I thought it might be good to ask
at a high level.
Does this encrypt only the RTSP part of the conversation? Is the video
still in the clear?
I know there are 3 ways to stream in live555, TCP interleave, tunneled and
UDP.
Did we get SRTP and SRTCP in this
> I am working on special case where UDP is blocked and only outgoing
> port 443 is opened. So that RTSP client only able to open RTSP stream
> over SSL connection. I can pass socket descriptor of pre established
> SSL connection to RTSPClient class, but SSL calls are not implemented
> in groupsock
Hi,
I am working on special case where UDP is blocked and only outgoing
port 443 is opened. So that RTSP client only able to open RTSP stream
over SSL connection. I can pass socket descriptor of pre established
SSL connection to RTSPClient class, but SSL calls are not implemented
in groupsock to r
