> On Jul 19, 2025, at 11:28 AM, BENMOUSSA Yahia - Contractor via live-devel > <[email protected]> wrote: > > > From: BENMOUSSA Yahia - Contractor <[email protected]> > Subject: RE: [Live-devel] RTSPS and PKI > Date: July 19, 2025 at 11:28:54 AM GMT+2 > To: LIVE555 Streaming Media - development & use <[email protected]> > > > Classified as: {OPEN} > > I don't understand how to implement ClientTLSState::setupExtra without having > to modify the source code.
If possible, I will update the supplied code to make it possible to do what you want. However, I will not be doing the following: > Most TLS clients offer the option of using a private CA file. It would be > nice if live555 could do this. We do not provide a general “TLS client”. We provide a RTSP client, that can (optionally) use TLS to set up a RTSP connection. A client accesses a RTSP connection using a “rtsp://“ or “rtsps://“ URL - only. There is no provision in the RTSP protocol for a client to also use its own certificate file, in addition to the URL. (This is just like HTTP - a web browser uses just a URL; it doesn’t also use a certificate file.) Allowing the client to do this would be creating a new, non-standard protocol. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
