First utility for me is that it passes across most firewalls, ie i cannot access any regular red5 app (rtmp over 1835) from work.
On 7/24/07, Ben Wade <[EMAIL PROTECTED]> wrote:
Hi Jason and Alexandre, I have several questions. What is the reason for having rtmps on red5 streaming? I imagine it's a security thing, so what sort of security breach would this prevent. Also, would streaming be slower over ssl due to the encryption process? Lastly, should most people be using red5 with stunnel/rtmps enabled with their red5 installation? Or is it more of an experimental / beta optional project at this point? Sorry for all the questions, I probably sound like a 4 year old. Thanks, ben Wade ------------------------------ *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Alexandre Chapellon *Sent:* Wednesday, July 18, 2007 11:49 AM *To:* [email protected] *Subject:* Re: [Red5] RTMPS with stunnel Hi Jason thx for help! mod_proxy was great idea to get rid of your problem. I finally succeed in setting up rtmpS but I used the built-in SSL function of the red5 server! Anyway my problem using IE was only a certificate problem. By the way I'm still unable to complete an rtmpS (it works with rtmp and rtmpt) connection using the Adobe Flash plugin for Linux! If you have information about it... I'd love that! 2007/7/18, Jason Powell <[EMAIL PROTECTED]>: Hey Alex, sorry if someone already helped you with this, but my Red5 server lives behind a firewall, but I've managed to get both RTMPT and RTMPS working. I had the same problems you did with stunnel, but my "firewall" machine also serves as a mail/web server, so I created a virtual host in Apache that proxies certain URLs (if you search the list archive you should find them, I think they're /open /close /idle and /send) to the RTMPT port of my Red5 server using mod_proxy, ie: ProxyPass /open http://my.internal.red5.server:8088/open I did that for both <VirtualHost blah> and <VirtualHost blah:443>. Jason Alexandre Chapellon wrote: > Hi all, > > I'm actually trying to setup an rtmps video stream. > rtmp in a web page works great on all browsers (well all I have tested!) ; > rtmpt too! > Setting up SSL over rtmp was far more complex and time consuming... > > I am using stunnel to achieve SSL over rtmpt. > Here is my stunnel.conf: > ######################################################## > cert = /etc/ssl/certs/stunnel.pem > sslVersion = SSLv3 > chroot = /var/lib/stunnel4/ > > setuid = stunnel4 > setgid = stunnel4 > pid = /stunnel4.pid > socket = l:TCP_NODELAY=0 > socket = r:TCP_NODELAY=0 > debug = 7 > [rtmps] > TIMEOUTconnect = 0 > accept = 443 > connect = 8443 > TIMEOUTclose = 0 > > ######################################################## > > This config work for forwarding 443 to 80 (regular HTTPS) > But when I try to forward to rtmpt here is what I get: > > - works on Firefox / windows > - fails on Firefox / linux > - fails on IE7 / windows XP > > > I have two completly differents errors for the two failing setups: > > - On IE7 / windows, stunnel seems to tell everything is going well but I > never see the Flash plugin popup about security. (I have a popup about > > security because of autosigned SSL, but that's all.) > > - On Firefox / Linux stunnel tells me "the peer suddenly disconnected"! > here follow the logs: > > ###################################################### > > 2007.07.13 19:13:25 LOG7[20511:3083531968]: rtmps - https accepted FD=7 from > 21.1.15.2:44167 <http://21.1.15.2:44167> > 2007.07.13 19:13:25 LOG7[20511:3083406256]: rtmps - https started > 2007.07.13 19:13:25 LOG7[20511:3083406256]: FD 7 in non-blocking mode > > 2007.07.13 19:13:25 LOG7[20511:3083406256]: TCP_NODELAY option set on local > socket > 2007.07.13 19:13:25 LOG7[20511:3083406256]: FD 8 in non-blocking mode > 2007.07.13 19:13:25 LOG7[20511:3083406256]: FD 9 in non-blocking mode > > 2007.07.13 19:13:25 LOG7[20511:3083531968]: Cleaning up the signal pipe > 2007.07.13 19:13:25 LOG6[20511:3083531968]: Child process 20534 finished > with code 0 > 2007.07.13 19:13:25 LOG7[20511:3083406256]: Connection from > 21.1.15.2:44167 <http://21.1.15.2:44167> > permitted by libwrap > 2007.07.13 19:13:25 LOG5[20511:3083406256]: rtmps - https connected from > 21.1.15.2:44167 <http://21.1.15.2:44167> > 2007.07.13 > 19:13:25 LOG7[20511:3083406256]: SSL state (accept): > before/accept initialization > 2007.07.13 19:13:25 LOG3[20511:3083406256]: SSL_accept: Peer suddenly > disconnected > 2007.07.13 19:13:25 LOG5[20511:3083406256]: Connection reset: 0 bytes sent > > to SSL, 0 bytes sent to socket > 2007.07.13 19:13:25 LOG7[20511:3083406256]: rtmps - https finished (0 left) > ####################################################### > > Does anyone experienced such behaviour? Is it a RED5 limitation? is there a > > workaround? Am I a fool? > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
-- ------------------------------------------------------------------- If a man speaks in a forest and his wife is not there, is he still wrong?
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
