subject:"Re\: RTMPS"

RE: [openmeetings-user] Re: RTMPS

2011-12-05 Thread Holger Rabbach (ICT)

Hi,

There is RTMPS documentation at 
http://code.google.com/p/openmeetings/wiki/RTMPSandHTTPS, but in only works 
with trunk or the nightly builds at the moment, as far as I know.

Holger




-Original Message-
From: openmeetings-user@googlegroups.com 
[mailto:openmeetings-user@googlegroups.com] On Behalf Of dormitilla
Sent: Freitag, 2. Dezember 2011 19:33
To: OpenMeetings User
Subject: [openmeetings-user] Re: RTMPS

Hello,
is there a useable RTMPS implementation in the actual OM version, or have I to 
change the sourcecode, like it was adivsed in some older postings, to get it 
working.

@Holger Rabbach: Could you please write down your a detailed step by step 
information?

Best Regards
Ed

On 19 Okt., 17:55, nexus  wrote:
> Sorry for the late reply, but I'm glad you got it working. I just put
> the HTTPS part in case you wanted it, but like Sebastian said it is
> not needed since little data is transferred over HTTP. I don't use it
> myself for openmeetings, but have used for other projects such as
> using a Java-PHP bridge in Red5.
>
> On Oct 18, 8:54 am, "seba.wag...@gmail.com" 
> wrote:
>
>
>
> > If you are usingRTMPSthe password from the OpenMeetings client to
> >the  server is already encrypted.
> >RTMPSis used not only for the video part but also for all DATA
> >laoding/RPC/RMI like calls.
>
> > The only additional thing you will encrypt by using HTTPS instead of
> > HTTP is sending profile images, download/pload documents and loading
> > the SWF/html file with the application from the server encrypted.
>
> > Sebastian
>
> > 2011/10/18 Holger Rabbach (ICT) 
>
> > >  Hi Ed,
>
> > > ** **
>
> > > All I really did was follow the instructions in the document
> > > attached to issue 1543 in the issue tracker (and apply some manual
> > > "error correction" to it). I'm still running the HTTP part
> > > unencrypted at the moment, but plan to switch to HTTPS soon - I
> > > guess that should also close the unencrypted password gap.
>
> > > ** **
>
> > > Best regards,
>
> > > Holger
>
> > > ** **
>
> > > [image: Description: holger-rabbach]
>
> > > ** **
>
> > > *From:* openmeetings-user@googlegroups.com [mailto:
> > > openmeetings-user@googlegroups.com] *On Behalf Of
> > > *dormiti...@gmx.de
> > > *Sent:* Dienstag, 18. Oktober 2011 12:26
> > > *To:* openmeetings-user@googlegroups.com
> > > *Subject:* Re: [openmeetings-user] Re:RTMPS
>
> > > ** **
>
> > > Hello Holger,
>
> > >  
>
> > > congratulations, you got it working. 
>
> > > We also tried to secure the use of openmeetings withRTMPSfor our
> > > schoolnetwork, but our work failed. So, for example, the ldap
> > > password is submitted unencrypted. :-(
>
> > >  
>
> > > Could you write down - from the beginning to the end - how you got
> > > it working. 
>
> > > It would be so helpful.
>
> > > In the moment, there are so much places with partial informations
> > > and the last pice of the chain is always missing.
>
> > >  
>
> > > Thanks in advance.
>
> > >  
>
> > > Greatings
>
> > >  
>
> > > Ed
>
> > > --
> > > You received this message because you are subscribed to the Google
> > >Groups  "OpenMeetings User" group.
> > > To view this discussion on the web visit
> > >https://groups.google.com/d/msg/openmeetings-user/-/ibkIud3kMVEJ.
> > > To post to this group, send email to openmeetings-user@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > openmeetings-user+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/openmeetings-user?hl=en.
>
> > > --
> > > OM International Limited - Unit B Clifford Court, Cooper Way -
> > > Carlisle CA3 0JG - United Kingdom Charity reg no: 1112655 -
> > > Company reg no: 5649412 (England and Wales)
>
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "OpenMeetings User" group.
> > > To post to this group, send email to openmeetings-user@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > openmeetings-user+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://gro

[openmeetings-user] Re: RTMPS

2011-12-02 Thread dormitilla

Hello,
is there a useable RTMPS implementation in the actual OM version, or
have I to change the sourcecode, like it was adivsed in some older
postings, to get it working.

@Holger Rabbach: Could you please write down your a detailed step by
step information?

Best Regards
Ed

On 19 Okt., 17:55, nexus  wrote:
> Sorry for the late reply, but I'm glad you got it working. I just put
> the HTTPS part in case you wanted it, but like Sebastian said it is
> not needed since little data is transferred over HTTP. I don't use it
> myself for openmeetings, but have used for other projects such as
> using a Java-PHP bridge in Red5.
>
> On Oct 18, 8:54 am, "seba.wag...@gmail.com" 
> wrote:
>
>
>
> > If you are usingRTMPSthe password from the OpenMeetings client to the
> > server is already encrypted.
> >RTMPSis used not only for the video part but also for all DATA
> > laoding/RPC/RMI like calls.
>
> > The only additional thing you will encrypt by using HTTPS instead of HTTP is
> > sending profile images, download/pload documents and loading the SWF/html
> > file with the application from the server encrypted.
>
> > Sebastian
>
> > 2011/10/18 Holger Rabbach (ICT) 
>
> > >  Hi Ed,
>
> > > ** **
>
> > > All I really did was follow the instructions in the document attached to
> > > issue 1543 in the issue tracker (and apply some manual “error correction” 
> > > to
> > > it). I’m still running the HTTP part unencrypted at the moment, but plan 
> > > to
> > > switch to HTTPS soon - I guess that should also close the unencrypted
> > > password gap.
>
> > > ** **
>
> > > Best regards,
>
> > > Holger
>
> > > ** **
>
> > > [image: Description: holger-rabbach]
>
> > > ** **
>
> > > *From:* openmeetings-user@googlegroups.com [mailto:
> > > openmeetings-user@googlegroups.com] *On Behalf Of *dormiti...@gmx.de
> > > *Sent:* Dienstag, 18. Oktober 2011 12:26
> > > *To:* openmeetings-user@googlegroups.com
> > > *Subject:* Re: [openmeetings-user] Re:RTMPS
>
> > > ** **
>
> > > Hello Holger,
>
> > >  
>
> > > congratulations, you got it working. 
>
> > > We also tried to secure the use of openmeetings withRTMPSfor our
> > > schoolnetwork, but our work failed. So, for example, the ldap password is
> > > submitted unencrypted. :-(
>
> > >  
>
> > > Could you write down - from the beginning to the end - how you got it
> > > working. 
>
> > > It would be so helpful.
>
> > > In the moment, there are so much places with partial informations and the
> > > last pice of the chain is always missing.
>
> > >  
>
> > > Thanks in advance.
>
> > >  
>
> > > Greatings
>
> > >  
>
> > > Ed
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "OpenMeetings User" group.
> > > To view this discussion on the web visit
> > >https://groups.google.com/d/msg/openmeetings-user/-/ibkIud3kMVEJ.
> > > To post to this group, send email to openmeetings-user@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > openmeetings-user+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/openmeetings-user?hl=en.
>
> > > --
> > > OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle 
> > > CA3
> > > 0JG - United Kingdom
> > > Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "OpenMeetings User" group.
> > > To post to this group, send email to openmeetings-user@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > openmeetings-user+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/openmeetings-user?hl=en.
>
> > --
> > Sebastian 
> > Wagnerhttp://www.openmeetings.dehttp://www.webbase-design.dehttp://www.wagn...
> > seba.wag...@gmail.com
>
> >  image001.jpg
> > 28KViewDownload- Hide quoted text -
>
> > - Show quoted text -- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

[openmeetings-user] Re: RTMPS

2011-10-19 Thread nexus

Sorry for the late reply, but I'm glad you got it working. I just put
the HTTPS part in case you wanted it, but like Sebastian said it is
not needed since little data is transferred over HTTP. I don't use it
myself for openmeetings, but have used for other projects such as
using a Java-PHP bridge in Red5.

On Oct 18, 8:54 am, "seba.wag...@gmail.com" 
wrote:
> If you are using RTMPS the password from the OpenMeetings client to the
> server is already encrypted.
> RTMPS is used not only for the video part but also for all DATA
> laoding/RPC/RMI like calls.
>
> The only additional thing you will encrypt by using HTTPS instead of HTTP is
> sending profile images, download/pload documents and loading the SWF/html
> file with the application from the server encrypted.
>
> Sebastian
>
> 2011/10/18 Holger Rabbach (ICT) 
>
>
>
>
>
> >  Hi Ed,
>
> > ** **
>
> > All I really did was follow the instructions in the document attached to
> > issue 1543 in the issue tracker (and apply some manual “error correction” to
> > it). I’m still running the HTTP part unencrypted at the moment, but plan to
> > switch to HTTPS soon - I guess that should also close the unencrypted
> > password gap.
>
> > ** **
>
> > Best regards,
>
> > Holger
>
> > ** **
>
> > [image: Description: holger-rabbach]
>
> > ** **
>
> > *From:* openmeetings-user@googlegroups.com [mailto:
> > openmeetings-user@googlegroups.com] *On Behalf Of *dormiti...@gmx.de
> > *Sent:* Dienstag, 18. Oktober 2011 12:26
> > *To:* openmeetings-user@googlegroups.com
> > *Subject:* Re: [openmeetings-user] Re: RTMPS
>
> > ** **
>
> > Hello Holger,
>
> >  
>
> > congratulations, you got it working. 
>
> > We also tried to secure the use of openmeetings with RTMPS for our
> > schoolnetwork, but our work failed. So, for example, the ldap password is
> > submitted unencrypted. :-(
>
> >  
>
> > Could you write down - from the beginning to the end - how you got it
> > working. 
>
> > It would be so helpful.
>
> > In the moment, there are so much places with partial informations and the
> > last pice of the chain is always missing.
>
> >  
>
> > Thanks in advance.
>
> >  
>
> > Greatings
>
> >  
>
> > Ed
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To view this discussion on the web visit
> >https://groups.google.com/d/msg/openmeetings-user/-/ibkIud3kMVEJ.
> > To post to this group, send email to openmeetings-user@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-user+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> > --
> > OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3
> > 0JG - United Kingdom
> > Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to openmeetings-user@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-user+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian 
> Wagnerhttp://www.openmeetings.dehttp://www.webbase-design.dehttp://www.wagner-sebastian.com
> seba.wag...@gmail.com
>
>  image001.jpg
> 28KViewDownload- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Re: [openmeetings-user] Re: RTMPS

2011-10-18 Thread seba.wag...@gmail.com

If you are using RTMPS the password from the OpenMeetings client to the
server is already encrypted.
RTMPS is used not only for the video part but also for all DATA
laoding/RPC/RMI like calls.

The only additional thing you will encrypt by using HTTPS instead of HTTP is
sending profile images, download/pload documents and loading the SWF/html
file with the application from the server encrypted.

Sebastian

2011/10/18 Holger Rabbach (ICT) 

>  Hi Ed,
>
> ** **
>
> All I really did was follow the instructions in the document attached to
> issue 1543 in the issue tracker (and apply some manual “error correction” to
> it). I’m still running the HTTP part unencrypted at the moment, but plan to
> switch to HTTPS soon - I guess that should also close the unencrypted
> password gap.
>
> ** **
>
> Best regards,
>
> Holger
>
> ** **
>
> [image: Description: holger-rabbach]
>
> ** **
>
> *From:* openmeetings-user@googlegroups.com [mailto:
> openmeetings-user@googlegroups.com] *On Behalf Of *dormiti...@gmx.de
> *Sent:* Dienstag, 18. Oktober 2011 12:26
> *To:* openmeetings-user@googlegroups.com
> *Subject:* Re: [openmeetings-user] Re: RTMPS
>
> ** **
>
> Hello Holger,
>
>  
>
> congratulations, you got it working. 
>
> We also tried to secure the use of openmeetings with RTMPS for our
> schoolnetwork, but our work failed. So, for example, the ldap password is
> submitted unencrypted. :-(
>
>  
>
> Could you write down - from the beginning to the end - how you got it
> working. 
>
> It would be so helpful.
>
> In the moment, there are so much places with partial informations and the
> last pice of the chain is always missing.
>
>  
>
> Thanks in advance.
>
>  
>
> Greatings
>
>  
>
> Ed
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/openmeetings-user/-/ibkIud3kMVEJ.
> To post to this group, send email to openmeetings-user@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3
> 0JG - United Kingdom
> Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to openmeetings-user@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>



-- 
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wag...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

<>

RE: [openmeetings-user] Re: RTMPS

2011-10-18 Thread Holger Rabbach (ICT)

Hi Ed,

All I really did was follow the instructions in the document attached to issue 
1543 in the issue tracker (and apply some manual "error correction" to it). I'm 
still running the HTTP part unencrypted at the moment, but plan to switch to 
HTTPS soon - I guess that should also close the unencrypted password gap.

Best regards,
Holger

[cid:image001.jpg@01CC8DA4.90CB7E70]

From: openmeetings-user@googlegroups.com 
[mailto:openmeetings-user@googlegroups.com] On Behalf Of dormiti...@gmx.de
Sent: Dienstag, 18. Oktober 2011 12:26
To: openmeetings-user@googlegroups.com
Subject: Re: [openmeetings-user] Re: RTMPS

Hello Holger,

congratulations, you got it working.
We also tried to secure the use of openmeetings with RTMPS for our 
schoolnetwork, but our work failed. So, for example, the ldap password is 
submitted unencrypted. :-(

Could you write down - from the beginning to the end - how you got it working.
It would be so helpful.
In the moment, there are so much places with partial informations and the last 
pice of the chain is always missing.

Thanks in advance.

Greatings

Ed
--
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/openmeetings-user/-/ibkIud3kMVEJ.
To post to this group, send email to 
openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com>.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com<mailto:openmeetings-user+unsubscr...@googlegroups.com>.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.


OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 0JG 
- United Kingdom
Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

<>

Re: [openmeetings-user] Re: RTMPS

2011-10-18 Thread dormiti...@gmx.de

Hello Holger,
 
congratulations, you got it working. 
We also tried to secure the use of openmeetings with RTMPS for our 
schoolnetwork, but our work failed. So, for example, the ldap password is 
submitted unencrypted. :-(
 
Could you write down - from the beginning to the end - how you got it 
working. 
It would be so helpful.
In the moment, there are so much places with partial informations and the 
last pice of the chain is always missing.
 
Thanks in advance.
 
Greatings
 
Ed

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/openmeetings-user/-/ibkIud3kMVEJ.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

RE: [openmeetings-user] Re: RTMPS

2011-10-16 Thread Holger Rabbach (ICT)

Thanks, looks very helpful - you have a typo in the second step - at that point 
you want to edit the .properties files - maybe in the next revision you want to 
fix that :)

Best regards,
Holger



-Original Message-
From: openmeetings-user@googlegroups.com 
[mailto:openmeetings-user@googlegroups.com] On Behalf Of nexus
Sent: Samstag, 15. Oktober 2011 19:47
To: OpenMeetings User
Subject: [openmeetings-user] Re: RTMPS

Sebastian,

I have submitted the RTMPS setup guide that I posted a while back under Issue 
1543. I couldn't find another place to upload it to. I think that I am getting 
close on an RTMPS client. The origianl issue I ran into was that the 
red5-screenshare was getting compiled against an older red5.jar that did not 
have the RTMPSClient, it was using the older TomcatRTMPS which I believe is 
RTMP tunneled over HTTPS. I then compiled the client against the newer red5.jar 
included in Red5 1.0RC1 with a minor modification and the client does compile. 
After compiling it and running the client, I was getting some classes not found 
errors to do with logging that has changed in Red5 1.0RC1. I then updated the 
logback.jar that the screenshare client is compiled against which eliminated 
those errors. Now, I am just getting errors associated with slf4j classes not 
being found. I am checking into that now and plan on doing some tests this 
week. I will post later in the week where I am at as well as any possible 
issues. I can post my source as well. I really love the work that you have done 
and wouldn't mind helping contributing towards this.

On Oct 13, 5:24 pm, "seba.wag...@gmail.com" 
wrote:
> @nexus: meanwhile maybe you could re-submit your initial document again?
> Btw: What did fail in your case with the RTMPSClient? I have submited 
> some problems to the forums but not yet clear what the result will be.
>
> Sebastian
>
> 2011/10/13 Holger Rabbach (ICT) 
>
>
>
>
>
> > Hi again,
>
> > Sorry to come back to this old message, but I'm still confused. I 
> > did edit the client source (to add the "best" proxy type), 
> > recompiled and installed it and I did import the certificate into 
> > the keystore. Running tcpdump on my server, I can see the only ports 
> > being used (and actually even attempted) are 5080 and 1935 - I can 
> > also see that all traffic is unencrypted. The client obviously never 
> > even tries any kind SSL connection. For debugging purposes, which 
> > ports would I expect to see traffic on if it worked? Or would it try 
> > to negotiate a TLS connection on port 1935? Unfortunately Google 
> > removed all the pages on Google Groups, so the short howto that 
> > Nexus put together last year is no longer available. I'm not getting 
> > anywhere here, even though I've tried various things already, 
> > including modifying red5-core.xml to include the beans needed for 
> > RTMPS (still, since the client never even tries to connect to that 
> > additional port, it would seem to make no difference). I'd just wait 
> > for the promised bits of documentation, but since I'm working on a 
> > prototype installation for a study project, I have a deadline 
> > hanging over my head and even though it wouldn't be the end of the 
> > world if I couldn't, it would be nice if I could actually 
> > demonstrate to my tutor that the required security mechanisms 
> > already work and aren't "going to work" at some later date :). Not 
> > trying to put any pressure on anyone here, just trying to explain why I'm 
> > so persistent in coming back to this topic. I really appreciate the amount 
> > of work that's going into OpenMeetings and the helpful responses here on 
> > this list.
>
> > Best regards,
> > Holger
>
> > -Original Message-
> > From: openmeetings-user@googlegroups.com [mailto:
> > openmeetings-user@googlegroups.com] On Behalf Of nexus
> > Sent: Samstag, 8. Oktober 2011 02:01
> > To: OpenMeetings User
> > Subject: [openmeetings-user] Re: RTMPS
>
> > On Oct 7, 9:52 am, "Holger Rabbach (ICT)" 
> > wrote:
> > > Hi Sebastian,
>
> > > Sounds good - screensharing and recording are not of high 
> > > importance at
> > this point, so I can live without them until this is fixed. I'll 
> > keep an eye open for the guide to be published. Thanks for your quick 
> > response.
>
> > > Holger
>
> > > [cid:image001@01CC8509.237C99B0]
>
> > > From: openmeetings-user@googlegroups.com
> > > [mailto:openmeetings-user@googlegroups.com] On Behalf Of 
> > > seba.wag...@gmail.com
> > > Sent: Freitag, 7

Re: [openmeetings-user] Re: RTMPS

2011-10-15 Thread seba.wag...@gmail.com

Hi Nexus,

sounds geat, let us know if there is an issue, maybe we do currently
work on the same things ^^

Sebastian

2011/10/15 nexus :
> Sebastian,
>
> I have submitted the RTMPS setup guide that I posted a while back
> under Issue 1543. I couldn't find another place to upload it to. I
> think that I am getting close on an RTMPS client. The origianl issue I
> ran into was that the red5-screenshare was getting compiled against an
> older red5.jar that did not have the RTMPSClient, it was using the
> older TomcatRTMPS which I believe is RTMP tunneled over HTTPS. I then
> compiled the client against the newer red5.jar included in Red5 1.0RC1
> with a minor modification and the client does compile. After compiling
> it and running the client, I was getting some classes not found errors
> to do with logging that has changed in Red5 1.0RC1. I then updated the
> logback.jar that the screenshare client is compiled against which
> eliminated those errors. Now, I am just getting errors associated with
> slf4j classes not being found. I am checking into that now and plan on
> doing some tests this week. I will post later in the week where I am
> at as well as any possible issues. I can post my source as well. I
> really love the work that you have done and wouldn't mind helping
> contributing towards this.
>
> On Oct 13, 5:24 pm, "seba.wag...@gmail.com" 
> wrote:
>> @nexus: meanwhile maybe you could re-submit your initial document again?
>> Btw: What did fail in your case with the RTMPSClient? I have submited some
>> problems to the forums but not yet clear what the result will be.
>>
>> Sebastian
>>
>> 2011/10/13 Holger Rabbach (ICT) 
>>
>>
>>
>>
>>
>> > Hi again,
>>
>> > Sorry to come back to this old message, but I'm still confused. I did edit
>> > the client source (to add the "best" proxy type), recompiled and installed
>> > it and I did import the certificate into the keystore. Running tcpdump on 
>> > my
>> > server, I can see the only ports being used (and actually even attempted)
>> > are 5080 and 1935 - I can also see that all traffic is unencrypted. The
>> > client obviously never even tries any kind SSL connection. For debugging
>> > purposes, which ports would I expect to see traffic on if it worked? Or
>> > would it try to negotiate a TLS connection on port 1935? Unfortunately
>> > Google removed all the pages on Google Groups, so the short howto that 
>> > Nexus
>> > put together last year is no longer available. I'm not getting anywhere
>> > here, even though I've tried various things already, including modifying
>> > red5-core.xml to include the beans needed for RTMPS (still, since the 
>> > client
>> > never even tries to connect to that additional port, it would seem to make
>> > no difference). I'd just wait for the promised bits of documentation, but
>> > since I'm working on a prototype installation for a study project, I have a
>> > deadline hanging over my head and even though it wouldn't be the end of the
>> > world if I couldn't, it would be nice if I could actually demonstrate to my
>> > tutor that the required security mechanisms already work and aren't "going
>> > to work" at some later date :). Not trying to put any pressure on anyone
>> > here, just trying to explain why I'm so persistent in coming back to this
>> > topic. I really appreciate the amount of work that's going into 
>> > OpenMeetings
>> > and the helpful responses here on this list.
>>
>> > Best regards,
>> > Holger
>>
>> > -Original Message-
>> > From: openmeetings-user@googlegroups.com [mailto:
>> > openmeetings-user@googlegroups.com] On Behalf Of nexus
>> > Sent: Samstag, 8. Oktober 2011 02:01
>> > To: OpenMeetings User
>> > Subject: [openmeetings-user] Re: RTMPS
>>
>> > On Oct 7, 9:52 am, "Holger Rabbach (ICT)" 
>> > wrote:
>> > > Hi Sebastian,
>>
>> > > Sounds good - screensharing and recording are not of high importance at
>> > this point, so I can live without them until this is fixed. I'll keep an 
>> > eye
>> > open for the guide to be published. Thanks for your quick response.
>>
>> > > Holger
>>
>> > > [cid:image001@01CC8509.237C99B0]
>>
>> > > From: openmeetings-user@googlegroups.com
>> > > [mailto:openmeetings-user@googlegroups.com] On Behalf Of
>> > > seba.wag...@gmail.com

[openmeetings-user] Re: RTMPS

2011-10-15 Thread nexus

Sebastian,

I have submitted the RTMPS setup guide that I posted a while back
under Issue 1543. I couldn't find another place to upload it to. I
think that I am getting close on an RTMPS client. The origianl issue I
ran into was that the red5-screenshare was getting compiled against an
older red5.jar that did not have the RTMPSClient, it was using the
older TomcatRTMPS which I believe is RTMP tunneled over HTTPS. I then
compiled the client against the newer red5.jar included in Red5 1.0RC1
with a minor modification and the client does compile. After compiling
it and running the client, I was getting some classes not found errors
to do with logging that has changed in Red5 1.0RC1. I then updated the
logback.jar that the screenshare client is compiled against which
eliminated those errors. Now, I am just getting errors associated with
slf4j classes not being found. I am checking into that now and plan on
doing some tests this week. I will post later in the week where I am
at as well as any possible issues. I can post my source as well. I
really love the work that you have done and wouldn't mind helping
contributing towards this.

On Oct 13, 5:24 pm, "seba.wag...@gmail.com" 
wrote:
> @nexus: meanwhile maybe you could re-submit your initial document again?
> Btw: What did fail in your case with the RTMPSClient? I have submited some
> problems to the forums but not yet clear what the result will be.
>
> Sebastian
>
> 2011/10/13 Holger Rabbach (ICT) 
>
>
>
>
>
> > Hi again,
>
> > Sorry to come back to this old message, but I'm still confused. I did edit
> > the client source (to add the "best" proxy type), recompiled and installed
> > it and I did import the certificate into the keystore. Running tcpdump on my
> > server, I can see the only ports being used (and actually even attempted)
> > are 5080 and 1935 - I can also see that all traffic is unencrypted. The
> > client obviously never even tries any kind SSL connection. For debugging
> > purposes, which ports would I expect to see traffic on if it worked? Or
> > would it try to negotiate a TLS connection on port 1935? Unfortunately
> > Google removed all the pages on Google Groups, so the short howto that Nexus
> > put together last year is no longer available. I'm not getting anywhere
> > here, even though I've tried various things already, including modifying
> > red5-core.xml to include the beans needed for RTMPS (still, since the client
> > never even tries to connect to that additional port, it would seem to make
> > no difference). I'd just wait for the promised bits of documentation, but
> > since I'm working on a prototype installation for a study project, I have a
> > deadline hanging over my head and even though it wouldn't be the end of the
> > world if I couldn't, it would be nice if I could actually demonstrate to my
> > tutor that the required security mechanisms already work and aren't "going
> > to work" at some later date :). Not trying to put any pressure on anyone
> > here, just trying to explain why I'm so persistent in coming back to this
> > topic. I really appreciate the amount of work that's going into OpenMeetings
> > and the helpful responses here on this list.
>
> > Best regards,
> > Holger
>
> > -Original Message-
> > From: openmeetings-user@googlegroups.com [mailto:
> > openmeetings-user@googlegroups.com] On Behalf Of nexus
> > Sent: Samstag, 8. Oktober 2011 02:01
> > To: OpenMeetings User
> > Subject: [openmeetings-user] Re: RTMPS
>
> > On Oct 7, 9:52 am, "Holger Rabbach (ICT)" 
> > wrote:
> > > Hi Sebastian,
>
> > > Sounds good - screensharing and recording are not of high importance at
> > this point, so I can live without them until this is fixed. I'll keep an eye
> > open for the guide to be published. Thanks for your quick response.
>
> > > Holger
>
> > > [cid:image001@01CC8509.237C99B0]
>
> > > From: openmeetings-user@googlegroups.com
> > > [mailto:openmeetings-user@googlegroups.com] On Behalf Of
> > > seba.wag...@gmail.com
> > > Sent: Freitag, 7. Oktober 2011 15:49
> > > To: openmeetings-user@googlegroups.com
> > > Subject: Re: [openmeetings-user] RTMPS
>
> > > Hallo Holger,
>
> > > you should use native SSL, we will publish a guide soon.
>
> > > However the screensharing and recording has no SSL feature yet.
> > > We hope to fix that when the guide is ready.
>
> > > Sebastian
> > > 2011/10/7 Holger mailto:holger.rabb...@om.org>>
> > > Hi,
>
> > > I've

Re: [openmeetings-user] Re: RTMPS

2011-10-13 Thread seba.wag...@gmail.com

@nexus: meanwhile maybe you could re-submit your initial document again?
Btw: What did fail in your case with the RTMPSClient? I have submited some
problems to the forums but not yet clear what the result will be.

Sebastian

2011/10/13 Holger Rabbach (ICT) 

> Hi again,
>
> Sorry to come back to this old message, but I'm still confused. I did edit
> the client source (to add the "best" proxy type), recompiled and installed
> it and I did import the certificate into the keystore. Running tcpdump on my
> server, I can see the only ports being used (and actually even attempted)
> are 5080 and 1935 - I can also see that all traffic is unencrypted. The
> client obviously never even tries any kind SSL connection. For debugging
> purposes, which ports would I expect to see traffic on if it worked? Or
> would it try to negotiate a TLS connection on port 1935? Unfortunately
> Google removed all the pages on Google Groups, so the short howto that Nexus
> put together last year is no longer available. I'm not getting anywhere
> here, even though I've tried various things already, including modifying
> red5-core.xml to include the beans needed for RTMPS (still, since the client
> never even tries to connect to that additional port, it would seem to make
> no difference). I'd just wait for the promised bits of documentation, but
> since I'm working on a prototype installation for a study project, I have a
> deadline hanging over my head and even though it wouldn't be the end of the
> world if I couldn't, it would be nice if I could actually demonstrate to my
> tutor that the required security mechanisms already work and aren't "going
> to work" at some later date :). Not trying to put any pressure on anyone
> here, just trying to explain why I'm so persistent in coming back to this
> topic. I really appreciate the amount of work that's going into OpenMeetings
> and the helpful responses here on this list.
>
> Best regards,
> Holger
>
>
>
>
> -Original Message-
> From: openmeetings-user@googlegroups.com [mailto:
> openmeetings-user@googlegroups.com] On Behalf Of nexus
> Sent: Samstag, 8. Oktober 2011 02:01
> To: OpenMeetings User
> Subject: [openmeetings-user] Re: RTMPS
>
>
>
> On Oct 7, 9:52 am, "Holger Rabbach (ICT)" 
> wrote:
> > Hi Sebastian,
> >
> > Sounds good - screensharing and recording are not of high importance at
> this point, so I can live without them until this is fixed. I'll keep an eye
> open for the guide to be published. Thanks for your quick response.
> >
> > Holger
> >
> > [cid:image001@01CC8509.237C99B0]
> >
> > From: openmeetings-user@googlegroups.com
> > [mailto:openmeetings-user@googlegroups.com] On Behalf Of
> > seba.wag...@gmail.com
> > Sent: Freitag, 7. Oktober 2011 15:49
> > To: openmeetings-user@googlegroups.com
> > Subject: Re: [openmeetings-user] RTMPS
> >
> > Hallo Holger,
> >
> > you should use native SSL, we will publish a guide soon.
> >
> > However the screensharing and recording has no SSL feature yet.
> > We hope to fix that when the guide is ready.
> >
> > Sebastian
> > 2011/10/7 Holger mailto:holger.rabb...@om.org>>
> > Hi,
> >
> > I've looked through the list archive quite a bit, but couldn't find a
> > solution to my problem there. I'm trying to use RTMPS in the latest
> > version of OpenMeetings (Windows clients only at this point), so I've
> > enabled RTMPS in red5 and in the client configuration. I have added a
> > valid certificate (plus CA and intermediate cert) to the keystore. I
> > can see that the client does indeed try to use RTMPS, but get the
> > following log message:
> >
> > [WARN] [Red5_Scheduler_Worker-2]
> > org.red5.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection
> > from 93.202.123.176 : 55110 to null (in: 294 out
> > 597 ), with id 1 due to long handshake
> >
> > I get the same message also if I try to use the builtin keystore
> > without my valid certificate - however, when I was using a password on
> > the certificate's key that was different from the keystore's, I got a
> > different error.
> >
> > Does RTMPS work at all? There was some talk on the list about "native"
> > RTMPS about a year ago, has that discussion led to any changes and are
> > they documented anywhere? Any help would be much appreciated - I'm
> > quite excited about OpenMeetings, but do need RTMPS support to be able
> > to use it.
> >
> > Best regards,
> > Holger
> >
> > --
&

RE: [openmeetings-user] Re: RTMPS

2011-10-13 Thread Holger Rabbach (ICT)

Hi again,

Sorry to come back to this old message, but I'm still confused. I did edit the 
client source (to add the "best" proxy type), recompiled and installed it and I 
did import the certificate into the keystore. Running tcpdump on my server, I 
can see the only ports being used (and actually even attempted) are 5080 and 
1935 - I can also see that all traffic is unencrypted. The client obviously 
never even tries any kind SSL connection. For debugging purposes, which ports 
would I expect to see traffic on if it worked? Or would it try to negotiate a 
TLS connection on port 1935? Unfortunately Google removed all the pages on 
Google Groups, so the short howto that Nexus put together last year is no 
longer available. I'm not getting anywhere here, even though I've tried various 
things already, including modifying red5-core.xml to include the beans needed 
for RTMPS (still, since the client never even tries to connect to that 
additional port, it would seem to make no difference). I'd just wait for the 
promised bits of documentation, but since I'm working on a prototype 
installation for a study project, I have a deadline hanging over my head and 
even though it wouldn't be the end of the world if I couldn't, it would be nice 
if I could actually demonstrate to my tutor that the required security 
mechanisms already work and aren't "going to work" at some later date :). Not 
trying to put any pressure on anyone here, just trying to explain why I'm so 
persistent in coming back to this topic. I really appreciate the amount of work 
that's going into OpenMeetings and the helpful responses here on this list.

Best regards,
Holger

-Original Message-
From: openmeetings-user@googlegroups.com 
[mailto:openmeetings-user@googlegroups.com] On Behalf Of nexus
Sent: Samstag, 8. Oktober 2011 02:01
To: OpenMeetings User
Subject: [openmeetings-user] Re: RTMPS

On Oct 7, 9:52 am, "Holger Rabbach (ICT)" 
wrote:
> Hi Sebastian,
>
> Sounds good - screensharing and recording are not of high importance at this 
> point, so I can live without them until this is fixed. I'll keep an eye open 
> for the guide to be published. Thanks for your quick response.
>
> Holger
>
> [cid:image001@01CC8509.237C99B0]
>
> From: openmeetings-user@googlegroups.com
> [mailto:openmeetings-user@googlegroups.com] On Behalf Of
> seba.wag...@gmail.com
> Sent: Freitag, 7. Oktober 2011 15:49
> To: openmeetings-user@googlegroups.com
> Subject: Re: [openmeetings-user] RTMPS
>
> Hallo Holger,
>
> you should use native SSL, we will publish a guide soon.
>
> However the screensharing and recording has no SSL feature yet.
> We hope to fix that when the guide is ready.
>
> Sebastian
> 2011/10/7 Holger mailto:holger.rabb...@om.org>>
> Hi,
>
> I've looked through the list archive quite a bit, but couldn't find a
> solution to my problem there. I'm trying to use RTMPS in the latest
> version of OpenMeetings (Windows clients only at this point), so I've
> enabled RTMPS in red5 and in the client configuration. I have added a
> valid certificate (plus CA and intermediate cert) to the keystore. I
> can see that the client does indeed try to use RTMPS, but get the
> following log message:
>
> [WARN] [Red5_Scheduler_Worker-2]
> org.red5.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection
> from 93.202.123.176 : 55110 to null (in: 294 out
> 597 ), with id 1 due to long handshake
>
> I get the same message also if I try to use the builtin keystore
> without my valid certificate - however, when I was using a password on
> the certificate's key that was different from the keystore's, I got a
> different error.
>
> Does RTMPS work at all? There was some talk on the list about "native"
> RTMPS about a year ago, has that discussion led to any changes and are
> they documented anywhere? Any help would be much appreciated - I'm
> quite excited about OpenMeetings, but do need RTMPS support to be able
> to use it.
>
> Best regards,
> Holger
>
> --
> You received this message because you are subscribed to the Google Groups 
> "OpenMeetings User" group.
> To post to this group, send email to 
> openmeetings-user@googlegroups.com<mailto:openmeetings-u...@googlegroups.com>.
> To unsubscribe from this group, send email to 
> openmeetings-user+unsubscr...@googlegroups.com<mailto:openmeetings-user%2Bunsubscr...@googlegroups.com>.
> For more options, visit this group 
> athttp://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian
> Wagnerhttp://www.openmeetings.dehttp://www.webbase-design.dehttp://www
> .wagner-sebastian.com
> seba.wag...@gmail.com<mailto:seba.wag...@gmail

RE: [openmeetings-user] Re: RTMPS

2011-10-10 Thread Holger Rabbach (ICT)

Hi Sebastian,

I thought that's what I had set up. I did change the source code and recompile. 
And looking at http://gregoire.org/2009/11/12/native-rtmps-in-red5/, that's 
pretty much what I did. Maybe a clarification is needed as to what the 
difference between RTMPS and native SSL is - I thought they were the same 
thing... even Nexus talks about "native RTMPS" in his mailing list posts from 
last year...

Holger

[cid:image001.jpg@01CC876A.940CC610]

, Oktober 2011 15:37
To: openmeetings-user@googlegroups.com
Subject: Re: [openmeetings-user] Re: RTMPS

Hallo Holger,

as Nexus did explain, he was using NATIVE SSL not RTMPS.
Also it does require to change source code and recompile that client.

Our guide will be quite similar to what Nexus has done.


Sebastian
2011/10/10 Holger Rabbach (ICT) 
mailto:holger.rabb...@om.org>>
PS: I also tried running red5 RTMPS on port 443 instead of 8443, just to be 
sure that's not the problem...




-Original Message-
From: 
openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com> 
[mailto:openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com>]
 On Behalf Of Holger Rabbach (ICT)
Sent: Montag, 10. Oktober 2011 15:18
To: 
openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com>
Subject: RE: [openmeetings-user] Re: RTMPS

Thanks, but that doesn't seem to work - I added the line, built a new 
distribution, installed it, ran the installer, then tried to connect from the 
client - doesn't even try port 8443. Emptied the browser cache as well, to be 
sure the old app isn't cached. Maybe this doesn't work anymore in 1.8.4?

Holger


-Original Message-
From: 
openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com> 
[mailto:openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com>]
 On Behalf Of nexus
Sent: Samstag, 8. Oktober 2011 02:01
To: OpenMeetings User
Subject: [openmeetings-user] Re: RTMPS

[...]

I did a lot of work a while back using RTMPS with Openmeetings and it works 
well. Sounds like you have the Red5 side set up. In order to get native SSL 
RTMPS to work with Openmeetings you have to checkout and download the source 
and add the following bit of code to the following
file: WebContent\openmeetings\base\remote\rtmpConnection.lzx

  this._nc = new NetConnection();

   // local reference to rtmpconnection
   this._nc.t = this;

   this._nc.proxyType = "best";--This is the line that
you have to add

After you add this line and build the app using the instructions on the build 
page, RTMPS will work.

In short, this line is necessary to tell the Flash player to try native SSL 
first before trying to go through other methods.

I have successfully used native SSL RTMPS using openmeetings with Windows, Mac, 
and Linux clients. It sounds like you have your keystore set up so this should 
be all you need.

I have been able to use the screensharer while using RTMPS but had to hard code 
the port in the source to use my RTMP port. So the screensharer has not been 
encrypted. I have recently been trying to build an RTMPS screensharer but have 
not been sucessful yet. I am looking forward to the guide mentioned as this 
should help with this quite a bit. I hope this is helpful.

--
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to 
openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com>.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com<mailto:openmeetings-user%2bunsubscr...@googlegroups.com>.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.


 OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 
0JG - United Kingdom
 Charity reg no: 1112655 - Company reg no: 5649412 (England and 
Wales)

--
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to 
openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com>.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com<mailto:openmeetings-user%2bunsubscr...@googlegroups.com>.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

--
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to 
openmeetings-user@googlegroups.com<mailto:openmeetings-user@googlegroups.com>.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com<mailto:openmeetings-user%2bunsubscr...@googlegroups.com>.
For more options, vis

[openmeetings-user] Re: RTMPS

2011-10-10 Thread nexus



On Oct 10, 9:37 am, "seba.wag...@gmail.com" 
wrote:
> Hallo Holger,
>
> as Nexus did explain, he was using NATIVE SSL not RTMPS.
> Also it does require to change source code and recompile that client.
>
> Our guide will be quite similar to what Nexus has done.
>
> Sebastian
>
> 2011/10/10 Holger Rabbach (ICT) 
>
>
>
>
>
> > PS: I also tried running red5 RTMPS on port 443 instead of 8443, just to be
> > sure that's not the problem...
>
> > -Original Message-
> > From: openmeetings-user@googlegroups.com [mailto:
> > openmeetings-user@googlegroups.com] On Behalf Of Holger Rabbach (ICT)
> > Sent: Montag, 10. Oktober 2011 15:18
> > To: openmeetings-user@googlegroups.com
> > Subject: RE: [openmeetings-user] Re: RTMPS
>
> > Thanks, but that doesn't seem to work - I added the line, built a new
> > distribution, installed it, ran the installer, then tried to connect from
> > the client - doesn't even try port 8443. Emptied the browser cache as well,
> > to be sure the old app isn't cached. Maybe this doesn't work anymore in
> > 1.8.4?
>
> > Holger
>
> > -Original Message-
> > From: openmeetings-user@googlegroups.com [mailto:
> > openmeetings-user@googlegroups.com] On Behalf Of nexus
> > Sent: Samstag, 8. Oktober 2011 02:01
> > To: OpenMeetings User
> > Subject: [openmeetings-user] Re: RTMPS
>
> > [...]
>
> > I did a lot of work a while back using RTMPS with Openmeetings and it works
> > well. Sounds like you have the Red5 side set up. In order to get native SSL
> > RTMPS to work with Openmeetings you have to checkout and download the source
> > and add the following bit of code to the following
> > file: WebContent\openmeetings\base\remote\rtmpConnection.lzx
>
> >           this._nc = new NetConnection();
>
> >            // local reference to rtmpconnection
> >            this._nc.t = this;
>
> >            this._nc.proxyType = "best";    --This is the line that
> > you have to add
>
> > After you add this line and build the app using the instructions on the
> > build page, RTMPS will work.
>
> > In short, this line is necessary to tell the Flash player to try native SSL
> > first before trying to go through other methods.
>
> > I have successfully used native SSL RTMPS using openmeetings with Windows,
> > Mac, and Linux clients. It sounds like you have your keystore set up so this
> > should be all you need.
>
> > I have been able to use the screensharer while using RTMPS but had to hard
> > code the port in the source to use my RTMP port. So the screensharer has not
> > been encrypted. I have recently been trying to build an RTMPS screensharer
> > but have not been sucessful yet. I am looking forward to the guide mentioned
> > as this should help with this quite a bit. I hope this is helpful.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to openmeetings-user@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-user+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> >  OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle
> > CA3 0JG - United Kingdom
> >  Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to openmeetings-user@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-user+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to openmeetings-user@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-user+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian 
> Wagnerhttp://www.openmeetings.dehttp://www.webbase-design.dehttp://www.wagner-sebastian.com
> seba.wag...@gmail.com- Hide quoted text -
>
> - Show quoted text -

Sebastian is correct. I have been using native SSL rather than RTM

Re: [openmeetings-user] Re: RTMPS

2011-10-10 Thread seba.wag...@gmail.com

Hallo Holger,

as Nexus did explain, he was using NATIVE SSL not RTMPS.
Also it does require to change source code and recompile that client.

Our guide will be quite similar to what Nexus has done.


Sebastian

2011/10/10 Holger Rabbach (ICT) 

> PS: I also tried running red5 RTMPS on port 443 instead of 8443, just to be
> sure that's not the problem...
>
>
>
>
> -Original Message-
> From: openmeetings-user@googlegroups.com [mailto:
> openmeetings-user@googlegroups.com] On Behalf Of Holger Rabbach (ICT)
> Sent: Montag, 10. Oktober 2011 15:18
> To: openmeetings-user@googlegroups.com
> Subject: RE: [openmeetings-user] Re: RTMPS
>
> Thanks, but that doesn't seem to work - I added the line, built a new
> distribution, installed it, ran the installer, then tried to connect from
> the client - doesn't even try port 8443. Emptied the browser cache as well,
> to be sure the old app isn't cached. Maybe this doesn't work anymore in
> 1.8.4?
>
> Holger
>
>
> -Original Message-
> From: openmeetings-user@googlegroups.com [mailto:
> openmeetings-user@googlegroups.com] On Behalf Of nexus
> Sent: Samstag, 8. Oktober 2011 02:01
> To: OpenMeetings User
> Subject: [openmeetings-user] Re: RTMPS
>
> [...]
>
> I did a lot of work a while back using RTMPS with Openmeetings and it works
> well. Sounds like you have the Red5 side set up. In order to get native SSL
> RTMPS to work with Openmeetings you have to checkout and download the source
> and add the following bit of code to the following
> file: WebContent\openmeetings\base\remote\rtmpConnection.lzx
>
>   this._nc = new NetConnection();
>
>// local reference to rtmpconnection
>this._nc.t = this;
>
>this._nc.proxyType = "best";--This is the line that
> you have to add
>
> After you add this line and build the app using the instructions on the
> build page, RTMPS will work.
>
> In short, this line is necessary to tell the Flash player to try native SSL
> first before trying to go through other methods.
>
> I have successfully used native SSL RTMPS using openmeetings with Windows,
> Mac, and Linux clients. It sounds like you have your keystore set up so this
> should be all you need.
>
> I have been able to use the screensharer while using RTMPS but had to hard
> code the port in the source to use my RTMP port. So the screensharer has not
> been encrypted. I have recently been trying to build an RTMPS screensharer
> but have not been sucessful yet. I am looking forward to the guide mentioned
> as this should help with this quite a bit. I hope this is helpful.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to openmeetings-user@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
>
>  OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle
> CA3 0JG - United Kingdom
>  Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to openmeetings-user@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to openmeetings-user@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
>


-- 
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wag...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

RE: [openmeetings-user] Re: RTMPS

2011-10-10 Thread Holger Rabbach (ICT)

PS: I also tried running red5 RTMPS on port 443 instead of 8443, just to be 
sure that's not the problem...




-Original Message-
From: openmeetings-user@googlegroups.com 
[mailto:openmeetings-user@googlegroups.com] On Behalf Of Holger Rabbach (ICT)
Sent: Montag, 10. Oktober 2011 15:18
To: openmeetings-user@googlegroups.com
Subject: RE: [openmeetings-user] Re: RTMPS

Thanks, but that doesn't seem to work - I added the line, built a new 
distribution, installed it, ran the installer, then tried to connect from the 
client - doesn't even try port 8443. Emptied the browser cache as well, to be 
sure the old app isn't cached. Maybe this doesn't work anymore in 1.8.4?

Holger


-Original Message-
From: openmeetings-user@googlegroups.com 
[mailto:openmeetings-user@googlegroups.com] On Behalf Of nexus
Sent: Samstag, 8. Oktober 2011 02:01
To: OpenMeetings User
Subject: [openmeetings-user] Re: RTMPS

[...]

I did a lot of work a while back using RTMPS with Openmeetings and it works 
well. Sounds like you have the Red5 side set up. In order to get native SSL 
RTMPS to work with Openmeetings you have to checkout and download the source 
and add the following bit of code to the following
file: WebContent\openmeetings\base\remote\rtmpConnection.lzx

   this._nc = new NetConnection();

// local reference to rtmpconnection
this._nc.t = this;

this._nc.proxyType = "best";--This is the line that
you have to add

After you add this line and build the app using the instructions on the build 
page, RTMPS will work.

In short, this line is necessary to tell the Flash player to try native SSL 
first before trying to go through other methods.

I have successfully used native SSL RTMPS using openmeetings with Windows, Mac, 
and Linux clients. It sounds like you have your keystore set up so this should 
be all you need.

I have been able to use the screensharer while using RTMPS but had to hard code 
the port in the source to use my RTMP port. So the screensharer has not been 
encrypted. I have recently been trying to build an RTMPS screensharer but have 
not been sucessful yet. I am looking forward to the guide mentioned as this 
should help with this quite a bit. I hope this is helpful.

--
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.


  OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 
0JG - United Kingdom
  Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

RE: [openmeetings-user] Re: RTMPS

2011-10-10 Thread Holger Rabbach (ICT)

Thanks, but that doesn't seem to work - I added the line, built a new 
distribution, installed it, ran the installer, then tried to connect from the 
client - doesn't even try port 8443. Emptied the browser cache as well, to be 
sure the old app isn't cached. Maybe this doesn't work anymore in 1.8.4?

Holger


-Original Message-
From: openmeetings-user@googlegroups.com 
[mailto:openmeetings-user@googlegroups.com] On Behalf Of nexus
Sent: Samstag, 8. Oktober 2011 02:01
To: OpenMeetings User
Subject: [openmeetings-user] Re: RTMPS

[...]

I did a lot of work a while back using RTMPS with Openmeetings and it works 
well. Sounds like you have the Red5 side set up. In order to get native SSL 
RTMPS to work with Openmeetings you have to checkout and download the source 
and add the following bit of code to the following
file: WebContent\openmeetings\base\remote\rtmpConnection.lzx

   this._nc = new NetConnection();

// local reference to rtmpconnection
this._nc.t = this;

this._nc.proxyType = "best";--This is the line that
you have to add

After you add this line and build the app using the instructions on the build 
page, RTMPS will work.

In short, this line is necessary to tell the Flash player to try native SSL 
first before trying to go through other methods.

I have successfully used native SSL RTMPS using openmeetings with Windows, Mac, 
and Linux clients. It sounds like you have your keystore set up so this should 
be all you need.

I have been able to use the screensharer while using RTMPS but had to hard code 
the port in the source to use my RTMP port. So the screensharer has not been 
encrypted. I have recently been trying to build an RTMPS screensharer but have 
not been sucessful yet. I am looking forward to the guide mentioned as this 
should help with this quite a bit. I hope this is helpful.

--
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.


  OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 
0JG - United Kingdom
  Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

[openmeetings-user] Re: RTMPS

2011-10-07 Thread nexus



On Oct 7, 9:52 am, "Holger Rabbach (ICT)" 
wrote:
> Hi Sebastian,
>
> Sounds good - screensharing and recording are not of high importance at this 
> point, so I can live without them until this is fixed. I'll keep an eye open 
> for the guide to be published. Thanks for your quick response.
>
> Holger
>
> [cid:image001@01CC8509.237C99B0]
>
> From: openmeetings-user@googlegroups.com 
> [mailto:openmeetings-user@googlegroups.com] On Behalf Of seba.wag...@gmail.com
> Sent: Freitag, 7. Oktober 2011 15:49
> To: openmeetings-user@googlegroups.com
> Subject: Re: [openmeetings-user] RTMPS
>
> Hallo Holger,
>
> you should use native SSL, we will publish a guide soon.
>
> However the screensharing and recording has no SSL feature yet.
> We hope to fix that when the guide is ready.
>
> Sebastian
> 2011/10/7 Holger mailto:holger.rabb...@om.org>>
> Hi,
>
> I've looked through the list archive quite a bit, but couldn't find a
> solution to my problem there. I'm trying to use RTMPS in the latest
> version of OpenMeetings (Windows clients only at this point), so I've
> enabled RTMPS in red5 and in the client configuration. I have added a
> valid certificate (plus CA and intermediate cert) to the keystore. I
> can see that the client does indeed try to use RTMPS, but get the
> following log message:
>
> [WARN] [Red5_Scheduler_Worker-2]
> org.red5.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection
> from 93.202.123.176 : 55110 to null (in: 294 out 597 ), 
> with id 1 due
> to long handshake
>
> I get the same message also if I try to use the builtin keystore
> without my valid certificate - however, when I was using a password on
> the certificate's key that was different from the keystore's, I got a
> different error.
>
> Does RTMPS work at all? There was some talk on the list about "native"
> RTMPS about a year ago, has that discussion led to any changes and are
> they documented anywhere? Any help would be much appreciated - I'm
> quite excited about OpenMeetings, but do need RTMPS support to be able
> to use it.
>
> Best regards,
> Holger
>
> --
> You received this message because you are subscribed to the Google Groups 
> "OpenMeetings User" group.
> To post to this group, send email to 
> openmeetings-user@googlegroups.com.
> To unsubscribe from this group, send email to 
> openmeetings-user+unsubscr...@googlegroups.com.
> For more options, visit this group 
> athttp://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian 
> Wagnerhttp://www.openmeetings.dehttp://www.webbase-design.dehttp://www.wagner-sebastian.com
> seba.wag...@gmail.com
> --
> You received this message because you are subscribed to the Google Groups 
> "OpenMeetings User" group.
> To post to this group, send email to 
> openmeetings-user@googlegroups.com.
> To unsubscribe from this group, send email to 
> openmeetings-user+unsubscr...@googlegroups.com.
> For more options, visit this group 
> athttp://groups.google.com/group/openmeetings-user?hl=en.
>
> 
> OM International Limited - Unit B Clifford Court, Cooper Way - Carlisle CA3 
> 0JG - United Kingdom
> Charity reg no: 1112655 - Company reg no: 5649412 (England and Wales)
>
>  image001.jpg
> 28KViewDownload

I did a lot of work a while back using RTMPS with Openmeetings and it
works well. Sounds like you have the Red5 side set up. In order to get
native SSL RTMPS to work with Openmeetings you have to checkout and
download the source and add the following bit of code to the following
file: WebContent\openmeetings\base\remote\rtmpConnection.lzx

   this._nc = new NetConnection();

// local reference to rtmpconnection
this._nc.t = this;

this._nc.proxyType = "best";--This is the line that
you have to add

After you add this line and build the app using the instructions on
the build page, RTMPS will work.

In short, this line is necessary to tell the Flash player to try
native SSL first before trying to go through other methods.

I have successfully used native SSL RTMPS using openmeetings with
Windows, Mac, and Linux clients. It sounds like you have your keystore
set up so this should be all you need.

I have been able to use the screensharer while using RTMPS but had to
hard code the port in the source to use my RTMP port. So the
screensharer has not been encrypted. I have recently been trying to
build an RTMPS screensharer but have not been sucessful yet. I am
looking forward to the guide mentioned as this should help with this
quite a bit. I hope this is helpful.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-user@googlegroups.com.
To unsubscribe from th

Re: RTMPS

2010-10-27 Thread seba.wag...@gmail.com

Yes the documentation contributed should still work.

Sebastian

2010/10/27 nicolas 

> Hi,
>
> I want run a openmmetings server with secure connection (SSL)
> I found this page [1] but it work's for the current version (1.5)?
>
> Regards
> Nicolas
>
> [1] : http://groups.google.com/group/openmeetings-user/web/rtmps-howto
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to openmeetings-u...@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
>


-- 
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.wagner-sebastian.com
seba.wag...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Re: RTMPS

2010-08-24 Thread nexus

You will first need to make sure that RTMPS is enabled and set up in
Red5 first and set up a keystore. I believe it is not enabled by
default. I have tried to put together an RTMPS Howto under the pages
section on the Openmeetings GoogleGroups page. Hopefully, this will be
helpful in setting this up.

On Aug 24, 11:11 am, Sebastian Wagner  wrote:
> search the google groups for openmeetings for *native rtmps*
>
> Sebastian
>
> 2010/8/24 Lancelot 
>
>
>
>
>
> > I've stopped red5 service and there is nothing else listening on port
> > 80 and 443.
>
> > What do you mean about "Have you really enabled the RTMPS Socket in
> > the configuration?". I'm missing a configuration?
>
> > I've read "native RTMPS" thread. I cannot understand what i need to
> > configure.
>
> > On 24 Ago, 09:53, Sebastian Wagner  wrote:
> > > Have you really enabled the RTMPS Socket in the configuration? Is there
> > > anything listening on port 443?
>
> > > Also have a look at the *native RTMPS* thread.
>
> > > Sebastian
>
> > > 2010/8/24 Lancelot 
>
> > > > I need to use openmeetings through internet and cannot use RTMP
> > > > because users ldap password are sent in plain text.
> > > > So I'm trying to use RTMPS (i've only windows clients). I'm using
> > > > OpenMeetings 1.3 RC1 r3264 on CentOS 5.5.
>
> > > > I've generated a self signed certificate with our Active Directory
> > > > Certification Authity using comands:
>
> > > >        keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -
> > > > keystore keystore
> > > >        keytool -certreq -alias red5 -keyalg RSA -file red5.csr -
> > > > keystore keystore
> > > >        ...
> > > >        keytool -import -alias root -keystore keystore -trustcacerts -
> > > > file certca.cer
> > > >        keytool -import -alias red5 -keystore keystore -trustcacerts -
> > > > file red5.cer
>
> > > > I've copied keystore file to conf folder.
>
> > > > I've modified conf/red5.properties file:
>
> > > >        # HTTP
> > > >        http.host=0.0.0.0
> > > >        #http.port=5080
> > > >        http.port=80
> > > >        #https.port=8443
> > > >        https.port=443
>
> > > >        ...
>
> > > >        # RTMPS
> > > >        rtmps.host=0.0.0.0
> > > >        #rtmps.port=8443
> > > >        rtmps.port=443
> > > >        rtmps.ping_interval=5000
> > > >        rtmps.max_inactivity=6
> > > >        rtmps.max_keep_alive_requests=-1
> > > >        rtmps.max_threads=20
> > > >        rtmps.acceptor_thread_count=2
> > > >        rtmps.processor_cache=20
> > > >        # RTMPS Keystore Password
> > > >        rtmps.keystorepass=**
>
> > > > I've also modified webapps/openmeetings/config.xml file:
>
> > > >        ...
> > > >        443
> > > >        ...
> > > >        yes
> > > >        ...
>
> > > > I've restarted red5 but clients fail using RTPMS on port 443 and then
> > > > use RTMPT on port 80.
> > > > What am I doing wrong?
>
> > > > Thanks.
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "OpenMeetings User" group.
> > > > To post to this group, send email to
> > openmeetings-u...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > openmeetings-user+unsubscr...@googlegroups.com
> > 
>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/openmeetings-user?hl=en.
>
> > > --
> > > Sebastian
> > Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://
> >www.wagner-sebastian.com
> > > seba.wag...@gmail.com
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to openmeetings-u...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-user+unsubscr...@googlegroups.com
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian 
> Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://www.wagner-sebastian.com
> seba.wag...@gmail.com- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Re: RTMPS

2010-08-24 Thread Sebastian Wagner

search the google groups for openmeetings for *native rtmps*

Sebastian

2010/8/24 Lancelot 

> I've stopped red5 service and there is nothing else listening on port
> 80 and 443.
>
> What do you mean about "Have you really enabled the RTMPS Socket in
> the configuration?". I'm missing a configuration?
>
> I've read "native RTMPS" thread. I cannot understand what i need to
> configure.
>
>
> On 24 Ago, 09:53, Sebastian Wagner  wrote:
> > Have you really enabled the RTMPS Socket in the configuration? Is there
> > anything listening on port 443?
> >
> > Also have a look at the *native RTMPS* thread.
> >
> > Sebastian
> >
> > 2010/8/24 Lancelot 
> >
> >
> >
> > > I need to use openmeetings through internet and cannot use RTMP
> > > because users ldap password are sent in plain text.
> > > So I'm trying to use RTMPS (i've only windows clients). I'm using
> > > OpenMeetings 1.3 RC1 r3264 on CentOS 5.5.
> >
> > > I've generated a self signed certificate with our Active Directory
> > > Certification Authity using comands:
> >
> > >keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -
> > > keystore keystore
> > >keytool -certreq -alias red5 -keyalg RSA -file red5.csr -
> > > keystore keystore
> > >...
> > >keytool -import -alias root -keystore keystore -trustcacerts -
> > > file certca.cer
> > >keytool -import -alias red5 -keystore keystore -trustcacerts -
> > > file red5.cer
> >
> > > I've copied keystore file to conf folder.
> >
> > > I've modified conf/red5.properties file:
> >
> > ># HTTP
> > >http.host=0.0.0.0
> > >#http.port=5080
> > >http.port=80
> > >#https.port=8443
> > >https.port=443
> >
> > >...
> >
> > ># RTMPS
> > >rtmps.host=0.0.0.0
> > >#rtmps.port=8443
> > >rtmps.port=443
> > >rtmps.ping_interval=5000
> > >rtmps.max_inactivity=6
> > >rtmps.max_keep_alive_requests=-1
> > >rtmps.max_threads=20
> > >rtmps.acceptor_thread_count=2
> > >rtmps.processor_cache=20
> > ># RTMPS Keystore Password
> > >rtmps.keystorepass=**
> >
> > > I've also modified webapps/openmeetings/config.xml file:
> >
> > >...
> > >443
> > >...
> > >yes
> > >...
> >
> > > I've restarted red5 but clients fail using RTPMS on port 443 and then
> > > use RTMPT on port 80.
> > > What am I doing wrong?
> >
> > > Thanks.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "OpenMeetings User" group.
> > > To post to this group, send email to
> openmeetings-u...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > openmeetings-user+unsubscr...@googlegroups.com
> 
> >
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/openmeetings-user?hl=en.
> >
> > --
> > Sebastian
> Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://
> www.wagner-sebastian.com
> > seba.wag...@gmail.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to openmeetings-u...@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
>


-- 
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.wagner-sebastian.com
seba.wag...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Re: RTMPS

2010-08-24 Thread Lancelot

I've stopped red5 service and there is nothing else listening on port
80 and 443.

What do you mean about "Have you really enabled the RTMPS Socket in
the configuration?". I'm missing a configuration?

I've read "native RTMPS" thread. I cannot understand what i need to
configure.


On 24 Ago, 09:53, Sebastian Wagner  wrote:
> Have you really enabled the RTMPS Socket in the configuration? Is there
> anything listening on port 443?
>
> Also have a look at the *native RTMPS* thread.
>
> Sebastian
>
> 2010/8/24 Lancelot 
>
>
>
> > I need to use openmeetings through internet and cannot use RTMP
> > because users ldap password are sent in plain text.
> > So I'm trying to use RTMPS (i've only windows clients). I'm using
> > OpenMeetings 1.3 RC1 r3264 on CentOS 5.5.
>
> > I've generated a self signed certificate with our Active Directory
> > Certification Authity using comands:
>
> >        keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -
> > keystore keystore
> >        keytool -certreq -alias red5 -keyalg RSA -file red5.csr -
> > keystore keystore
> >        ...
> >        keytool -import -alias root -keystore keystore -trustcacerts -
> > file certca.cer
> >        keytool -import -alias red5 -keystore keystore -trustcacerts -
> > file red5.cer
>
> > I've copied keystore file to conf folder.
>
> > I've modified conf/red5.properties file:
>
> >        # HTTP
> >        http.host=0.0.0.0
> >        #http.port=5080
> >        http.port=80
> >        #https.port=8443
> >        https.port=443
>
> >        ...
>
> >        # RTMPS
> >        rtmps.host=0.0.0.0
> >        #rtmps.port=8443
> >        rtmps.port=443
> >        rtmps.ping_interval=5000
> >        rtmps.max_inactivity=6
> >        rtmps.max_keep_alive_requests=-1
> >        rtmps.max_threads=20
> >        rtmps.acceptor_thread_count=2
> >        rtmps.processor_cache=20
> >        # RTMPS Keystore Password
> >        rtmps.keystorepass=**
>
> > I've also modified webapps/openmeetings/config.xml file:
>
> >        ...
> >        443
> >        ...
> >        yes
> >        ...
>
> > I've restarted red5 but clients fail using RTPMS on port 443 and then
> > use RTMPT on port 80.
> > What am I doing wrong?
>
> > Thanks.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenMeetings User" group.
> > To post to this group, send email to openmeetings-u...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > openmeetings-user+unsubscr...@googlegroups.com
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/openmeetings-user?hl=en.
>
> --
> Sebastian 
> Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://www.wagner-sebastian.com
> seba.wag...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Re: RTMPS

2010-08-24 Thread Sebastian Wagner

Have you really enabled the RTMPS Socket in the configuration? Is there
anything listening on port 443?

Also have a look at the *native RTMPS* thread.


Sebastian

2010/8/24 Lancelot 

> I need to use openmeetings through internet and cannot use RTMP
> because users ldap password are sent in plain text.
> So I'm trying to use RTMPS (i've only windows clients). I'm using
> OpenMeetings 1.3 RC1 r3264 on CentOS 5.5.
>
> I've generated a self signed certificate with our Active Directory
> Certification Authity using comands:
>
>keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -
> keystore keystore
>keytool -certreq -alias red5 -keyalg RSA -file red5.csr -
> keystore keystore
>...
>keytool -import -alias root -keystore keystore -trustcacerts -
> file certca.cer
>keytool -import -alias red5 -keystore keystore -trustcacerts -
> file red5.cer
>
> I've copied keystore file to conf folder.
>
> I've modified conf/red5.properties file:
>
># HTTP
>http.host=0.0.0.0
>#http.port=5080
>http.port=80
>#https.port=8443
>https.port=443
>
>...
>
># RTMPS
>rtmps.host=0.0.0.0
>#rtmps.port=8443
>rtmps.port=443
>rtmps.ping_interval=5000
>rtmps.max_inactivity=6
>rtmps.max_keep_alive_requests=-1
>rtmps.max_threads=20
>rtmps.acceptor_thread_count=2
>rtmps.processor_cache=20
># RTMPS Keystore Password
>rtmps.keystorepass=**
>
> I've also modified webapps/openmeetings/config.xml file:
>
>...
>443
>...
>yes
>...
>
> I've restarted red5 but clients fail using RTPMS on port 443 and then
> use RTMPT on port 80.
> What am I doing wrong?
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To post to this group, send email to openmeetings-u...@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-user+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>
>


-- 
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.wagner-sebastian.com
seba.wag...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Re: RTMPS and desktop sharing

2010-03-26 Thread Wiktor Zajas

After changing port to 1935 in both ScreenShareRTMPT.java and
ScreenShare.java, and executing 'ant -f build_red5webapp.xml dist',
everything works fine. I've checked netstat while using screenshare
applet and it was connected to 1935. I don't know, maybe it's because
I'm using svn version but i don't have time to dig in deeper.

On 26 Mar, 08:40, Wiktor Zajas  wrote:
> I've been thinking about some work-around, would it work if I comment
> line 180 in ScreenShareRTMPT.java. This way screenshare applet would
> work on default 8088 port, but I'm not sure if it will affect both
> listeners and viewers, but I do hope so :) Gonna try that today and
> see if I get results.
>
> On 24 Mar, 12:41, Wiktor Zajas  wrote:
>
>
>
> > Hi,
>
> > Should desktop sharing work with RTMPS ? Without ssl everything is ok, but
> > after enabling it, either sharing applet doesn't start at all or "Start
> > sharing" button won't turn to 'on'. I'm using r3087 and v4 of sharing
> > applet.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

Re: RTMPS and desktop sharing

2010-03-26 Thread Wiktor Zajas

I've been thinking about some work-around, would it work if I comment
line 180 in ScreenShareRTMPT.java. This way screenshare applet would
work on default 8088 port, but I'm not sure if it will affect both
listeners and viewers, but I do hope so :) Gonna try that today and
see if I get results.

On 24 Mar, 12:41, Wiktor Zajas  wrote:
> Hi,
>
> Should desktop sharing work with RTMPS ? Without ssl everything is ok, but
> after enabling it, either sharing applet doesn't start at all or "Start
> sharing" button won't turn to 'on'. I'm using r3087 and v4 of sharing
> applet.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings User" group.
To post to this group, send email to openmeetings-u...@googlegroups.com.
To unsubscribe from this group, send email to 
openmeetings-user+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/openmeetings-user?hl=en.

RE: [openmeetings-user] Re: RTMPS

[openmeetings-user] Re: RTMPS

[openmeetings-user] Re: RTMPS

Re: [openmeetings-user] Re: RTMPS

RE: [openmeetings-user] Re: RTMPS

Re: [openmeetings-user] Re: RTMPS

RE: [openmeetings-user] Re: RTMPS

Re: [openmeetings-user] Re: RTMPS

[openmeetings-user] Re: RTMPS

Re: [openmeetings-user] Re: RTMPS

RE: [openmeetings-user] Re: RTMPS

RE: [openmeetings-user] Re: RTMPS

[openmeetings-user] Re: RTMPS

Re: [openmeetings-user] Re: RTMPS

RE: [openmeetings-user] Re: RTMPS

RE: [openmeetings-user] Re: RTMPS

[openmeetings-user] Re: RTMPS

Re: RTMPS

Re: RTMPS

Re: RTMPS

Re: RTMPS

Re: RTMPS

Re: RTMPS and desktop sharing

Re: RTMPS and desktop sharing

24 matches

Site Navigation

Mail list logo

Footer information