*once you use the screen sharing function once and then close it OM hangs if you try and re-use it I'll check
*What’s the security implications of using one keystore in this instance Since keystore and password are passed unencrypted it is not good idea to use you server cetificate On Fri, May 18, 2012 at 7:01 PM, Stephen Cottham < [email protected]> wrote: > One thing to mention, once you use the screen sharing function once and > then close it OM hangs if you try and re-use it:**** > > ** ** > > All I get in the logs is this:**** > > ** ** > > [INFO] [NioProcessor-20] > org.red5.server.net.rtmp.codec.RTMPProtocolDecoder - Action connect**** > > [WARN] [Red5_Scheduler_Worker-1] org.red5.server.net.rtmp.RTMPConnection - > Closing RTMPMinaConnection from 10.17.23.28 : 11491 to > ukmeeting.robertbird.com:5443 (in: 4016 out 4447 ), with id 19 due to > long handshake**** > > [WARN] [Red5_Scheduler_Worker-2] org.red5.server.net.rtmp.RTMPConnection - > Closing RTMPMinaConnection from 10.17.23.28 : 11389 to > ukmeeting.robertbird.com:5443 (in: 837528 out 9656100 ), with id 17, due > to too much inactivity (182997 ms), last ping sent 999 ms ago**** > > [WARN] [Red5_Scheduler_Worker-2] org.red5.server.net.rtmp.RTMPConnection - > This often happens if YOUR Red5 application generated an exception on > start-up. Check earlier in the log for that exception first!**** > > [INFO] [Red5_Scheduler_Worker-2] > org.red5.server.stream.ClientBroadcastStream - Consumer disconnect**** > > [INFO] [Red5_Scheduler_Worker-2] > org.red5.server.stream.ClientBroadcastStream - Stream close**** > > [INFO] [Red5_Scheduler_Worker-2] > org.red5.server.stream.ClientBroadcastStream - Provider disconnect**** > > [INFO] [pool-4-thread-1] > org.openmeetings.app.remote.red5.ScopeApplicationAdapter - W3C > x-category:stream x-event:stop c-ip:10.17.23.28 cs-bytes:837528 > sc-bytes:9656100 x-sname:e2de090a-c38d-4a81-8116-67e4df778869**** > > [WARN] [Red5_Scheduler_Worker-1] org.red5.server.net.rtmp.RTMPConnection - > Closing RTMPMinaConnection from 10.17.23.28 : 11436 to > ukmeeting.robertbird.com:5443 (in: 876149 out 321723 ), with id 18, due > to too much inactivity (61001 ms), last ping sent 999 ms ago**** > > [WARN] [Red5_Scheduler_Worker-1] org.red5.server.net.rtmp.RTMPConnection - > This often happens if YOUR Red5 application generated an exception on > start-up. Check earlier in the log for that exception first!**** > > [INFO] [Red5_Scheduler_Worker-1] > org.red5.server.stream.ClientBroadcastStream - Stream close**** > > [INFO] [Red5_Scheduler_Worker-1] > org.red5.server.stream.ClientBroadcastStream - Provider disconnect**** > > [WARN] [Red5_Scheduler_Worker-3] org.red5.server.net.rtmp.RTMPConnection - > Closing RTMPMinaConnection from 10.17.23.35 : 52826 to > ukmeeting.robertbird.com:5443 (in: 48452 out 463893 ), with id 7, due to > too much inactivity (60999 ms), last ping sent 1001 ms ago**** > > [WARN] [Red5_Scheduler_Worker-3] org.red5.server.net.rtmp.RTMPConnection - > This often happens if YOUR Red5 application generated an exception on > start-up. Check earlier in the log for that exception first!**** > > ** ** > > No earlier exceptions in the logs either. **** > > ** ** > > Cheers**** > > ** ** > > ** ** > > ** ** > > *From:* Stephen Cottham > *Sent:* Friday, 18 May 2012 1:00 PM > > *To:* [email protected] > *Subject:* RE: RTMPSClient questions**** > > ** ** > > Hey Maxim,**** > > ** ** > > I’ve tested the latest build with HTTPS and RTMPS.**** > > ** ** > > Screen recording and screen sharing are working fine over encrypted > streams.**** > > ** ** > > What’s the security implications of using one keystore in this instance? > Assuming the password is hashed in the JNLP file before it connects?**** > > ** ** > > Looks good!**** > > ** ** > > ** ** > > *From:* Maxim Solodovnik [mailto:[email protected]] > *Sent:* Friday, 18 May 2012 12:24 PM > *To:* [email protected] > *Subject:* RE: RTMPSClient questions**** > > ** ** > > Since now MySQL JDBC driver is not included into bundle > > You need to manually download it > Or while building from the sources run "ant -Ddb=mysql"**** > > On May 18, 2012 6:20 PM, "Stephen Cottham" < > [email protected]> wrote:**** > > Hey Maxim,**** > > **** > > Im trying the latest build and getting the following error on start-up:*** > * > > **** > > ERROR 05-18 12:17:43.467 ScopeApplicationAdapter.java 7790 174 > org.openmeetings.app.remote.red5.ScopeApplicationAdapter > [Launcher:/openmeetings] - [appStart]**** > > org.springframework.transaction.CannotCreateTransactionException: Could > not open JPA EntityManager for transaction; nested exception is > <openjpa-2.2.0-r422266:1244990 fatal general error> > org.apache.openjpa.persistence.PersistenceException: Cannot load JDBC > driver class 'com.mysql.jdbc.Driver'**** > > **** > > Assuming issues talking with mysql, I can’t see any errors in the > persistence.xml file, got any idea what’s wrong here? I’ve dropped the DB > and recreated it, checked the UN and PW but same thing.**** > > **** > > Cheers**** > > **** > > **** > > **** > > *From:* Maxim Solodovnik [mailto:[email protected]] > *Sent:* Friday, 18 May 2012 11:46 AM > *To:* [email protected] > *Cc:* [email protected] > *Subject:* Re: RTMPSClient questions**** > > **** > > Yes**** > > this line need to be deleted/commented**** > > On Fri, May 18, 2012 at 5:37 PM, Stephen Cottham < > [email protected]> wrote:**** > > Hey Maxim,**** > > **** > > Seems we still need to comment the JMX line for this to work with RTMPS, > is that correct?**** > > **** > > **** > > **** > > *From:* Maxim Solodovnik [mailto:[email protected]] **** > > *Sent:* Thursday, 17 May 2012 6:15 PM**** > > *To:* [email protected]; > [email protected] > *Subject:* RTMPSClient questions**** > > **** > > Hello All,**** > > **** > > I seems to finish implementing RTMPS screen sharing client.**** > > To work it requires additional keystore "red5/conf/keystore.screen" with > the password specified in red5.properties: "rtmps.keystorepass" > **** > > **** > > Q1: how good to have same password for red5/conf/keystore > and red5/conf/keystore.screen? Should I add additional parameter to set up > separate password and customize keystore location?**** > > **** > > The specified keystore/password are passed to the screensharing applet via > <argument>: keystore as base64 encoded binary, password in plaintext.**** > > **** > > To avoid compromising "main" keystore I did the following:**** > > 1) create separate keystore (keystore.screen) with its own key**** > > 2) add key from 1 to "original" keystore**** > > **** > > Q2: Is this OK? Maybe anybody can suggest better (more secure) way of > handling it? Probably without second certificate?**** > > **** > > Thanks in advance**** > > **** > > -- > WBR > Maxim aka solomax**** > > *Stephen Cottham***** > > * > *Group IT Manager (Associate) > > Robert Bird Group > Level 5, 333 Ann St > Brisbane, Queensland, 4000, Australia**** > > *Phone: +6173 319 2777 (AUS)***** > > *Phone: +44207 592 8000 (UK)***** > > *Fax: +6173 319 2799***** > > **** > > *Mobile: +61400 756 963 (AUS)***** > > *Mobile: +447900 918 616 (UK)***** > > *Web: **www.robertbird.com* <http://www.robertbird.com/>**** > > <http://www.robertbird.com.au/> > > This email and any attachments are confidential and may contain legally > privileged information or copyright material. Unless expressly stated, > confidentiality and/or legal privilege is not intended to be waived by the > sending of this email. The contents of this email, including any > attachments, are intended solely for the use of the individual or entity to > whom they are addressed. If you are not an intended recipient, please > contact us immediately by return email and then delete both messages. You > may not otherwise read, forward, copy, use or disclose this email or any > attachments. Any views expressed in this email are those of the individual > sender except where the sender expressly, and with authority, states > otherwise. It is your responsibility to check any attachments for viruses > or defects before opening or sending them on. None of the sender or its > related entities accepts any liability for any consequential damage > resulting from this email containing computer viruses. **** > > **** > > > Disclaimer added by *CodeTwo Exchange Rules* > www.codetwo.com**** > > **** > > > > **** > > **** > > -- > WBR > Maxim aka solomax**** > -- WBR Maxim aka solomax
<<image001.gif>>
<<image002.png>>
