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:solomax...@gmail.com] Sent: Friday, 18 May 2012 12:24 PM To: openmeetings-user@incubator.apache.org 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" <stephen.cott...@robertbird.com.au> 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:solomax...@gmail.com] Sent: Friday, 18 May 2012 11:46 AM To: openmeetings-user@incubator.apache.org Cc: openmeetings-...@incubator.apache.org Subject: Re: RTMPSClient questions Yes this line need to be deleted/commented On Fri, May 18, 2012 at 5:37 PM, Stephen Cottham <stephen.cott...@robertbird.com.au> 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:solomax...@gmail.com] Sent: Thursday, 17 May 2012 6:15 PM To: openmeetings-...@incubator.apache.org; openmeetings-user@incubator.apache.org 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 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 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 http://www.codetwo.com
<<image001.gif>>
<<image002.png>>
