<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
<head>
<meta name="Generator" content="Zarafa WebApp v7.1.11-46050">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>RE: [Live-devel] Live555 support for RTSP over TLS</title>
</head>
<body>
<p style="padding: 0; margin: 0;"><span style="font-family: tahoma; font-size: 10pt;">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?<br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-family: tahoma; font-size: 10pt;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-family: tahoma; font-size: 10pt;">Thank you.<br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-family: tahoma; font-size: 10pt;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-family: tahoma; font-size: 10pt;">Bob<br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-family: tahoma; font-size: 10pt;"><br /></span></p>
<p style="padding: 0; margin: 0;"><span style="font-family: tahoma; font-size: 10pt;"><br /></span></p>
<div>
<blockquote style="border-left: 2px solid #325FBA; padding-left: 5px; margin: 0px 5px;"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 10pt;">-----Original message-----<br /><span><strong>From:</strong> Ross Finlayson <finlayson@live555.com></span><br /><span><strong>Sent:</strong> Thursday 6th October 2016 21:37</span><br /><span><strong>To:</strong> live555 Streaming Media - development & use <live-devel@ns.live555.com></span><br /><span><strong>Subject:</strong> Re: [Live-devel] Live555 support for RTSP over TLS</span><br /><br /></span>
<div>
<pre style="white-space: pre-wrap; word-wrap: break-word;">> It sounds like Gaurav wants to use Live555 w/ with a TLS socket for encrypted media transmission over a network.<br />> <br />> 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(…)).<br /><br />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.<br /><br />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.<br /><br /><br />Ross Finlayson<br />Live Networks, Inc.<br />http://www.live555.com/<br /><br /><br />_______________________________________________<br />live-devel mailing list<br />live-devel@lists.live555.com<br />http://lists.live555.com/mailman/listinfo/live-devel<br /></pre>
</div>
</blockquote>
</div>
</body>
</html>