The use case shown on your website here http://webrtc.live555.com/ is exactly what I need. But I would prefer to use Node.js as a web server. Is the source code for the LIVE555 WebRTC Proxy Server in the diagram available?
Thank you. Bob -----Original message----- From: Ross Finlayson <finlay...@live555.com> Sent: Thursday 6th October 2016 21:37 To: live555 Streaming Media - development & use <live-de...@ns.live555.com> Subject: Re: [Live-devel] Live555 support for RTSP over TLS > It sounds like Gaurav wants to use Live555 w/ with a TLS socket for encrypted > media transmission over a network. > > I could be incorrect, but since I have not seen a network abstraction in > place in the library, this would require either a fork of the library or some > nasty trickery to link socket calls (like sendto (…), recvfrom (…), etc) to > your own implementation that handles the TLS encryption. Creating a socket > that is used with a TLS protocol, then passing to Live555 would break the TLS > protocol as Live555 would send data that was not encrypted using TLS function > calls (like SSL_read/write(…)). Yes, I’ve been assuming that the underlying OS makes it possible to create a socket that can be read from/written to using regular socket I/O functions like “recvfrom()”/“sendto()” - i.e., with the underlying OS doing the requisite encryption/decryption automatically. But if, in fact, that’s not possible, and you require separate ‘user level’ socket I/O functions to read from/write to a TLS socket, then no, this cannot be done with our library. Sorry. 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
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
