I have just installed a new version (2021.11.14) of the “LIVE555 Streaming 
Media” code that allows a RTSP server to support connections via TLS.
To enable this, call:
        setTLSState(<certFileName>, <privKeyFileName>);
on your newly-created "RTSPServer" object (before you enter the event loop to 
start handling requests) - where <certFileName> is the (string) pathname of a 
certificate file, and <privKeyFileName> is the (string) pathname of a private 
key file - both in PEM format.  At present, this implementation does *not* 
serve SRTP (encrypted RTP/RTCP), and so does not accept "rtsps://" URLs.  (This 
will change in the future.)

If you want to access a (LIVE555) RTSP server via TLS using a LIVE555 RTSP 
client, then the server will need to be be running on port 322, otherwise the 
LIVE555 RTSP client implementation will not know that it needs to connect to 
the server using TLS.

(Of course, this requires OpenSSL, so will *not* work if you’re compiling with 
“-DNO_OPENSSL=1”.)


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/


_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to