Vsevolod, Here are Maxim fixes, http://code.google.com/p/red5/issues/detail?id=236
At least this is a good place to start digging this problem out. -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Dec 12, 2012 at 10:02 PM, Vsevolod <[email protected]> wrote: > I use file > apache-openmeetings-incubating-2.1.0.r1420479-11-12-2012_2328.tar.gz. Does > not it include this Red5 fixes from Maxim? Where can I find this fixes if > not? > > > Среда, 12 декабря 2012, 21:55 от Alexei Fedotov <[email protected]>: > > Vsevolod, > HTTPS didn't work well with screen sharing. Please ensure your release > contains Red5 fixes from Maxim. > > -- > With best regards / с наилучшими пожеланиями, > Alexei Fedotov / Алексей Федотов, > http://dataved.ru/ > +7 916 562 8095 > > > On Wed, Dec 12, 2012 at 5:37 PM, Всеволод Рябоконь <[email protected]> wrote: >> >> Hello! I have >> apache-openmeetings-incubating-2.1.0.r1420479-11-12-2012_2328.tar.gz from >> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/. I >> use it with https (port 8443) and rtmps (port 5443). Everything works but >> screensharing tool not. There is keystore conf/keystore.screen with same >> password and cert and alias file that in conf/keystore. Java application >> starts but if I click button "Start recording" or "Start sharing" nothing >> happens in application. Without conf/keystore.screen java application >> "Desktop sharer" does`nt start. >> I start red5 with >> , in red5.log i have messages that ends with >> -Djavax.net.debug=ssl,handshake,data and see many messages after press >> buttons, starting with >> >> "found key for : red5" and ending with >> >> trigger seeding of SecureRandom >> done seeding SecureRandom >> Using SSLEngineImpl. >> Allow unsafe renegotiation: false >> Allow legacy hello messages: true >> Is initial handshake: true >> Is secure renegotiation: false >> NioProcessor-46, called closeInbound() >> NioProcessor-46, fatal error: 80: Inbound closed before receiving peer's >> close_notify: possible truncation attack? >> javax.net.ssl.SSLException: Inbound closed before receiving peer's >> close_notify: possible truncation attack? >> NioProcessor-46, SEND TLSv1 ALERT: fatal, description = internal_error >> NioProcessor-46, WRITE: TLSv1 Alert, length = 2 >> NioProcessor-46, called closeOutbound() >> NioProcessor-46, closeOutboundInternal() >> >> On server: >> >> OS: Centos 6.3. >> >> java version "1.6.0_37" >> Java(TM) SE Runtime Environment (build 1.6.0_37-b06) >> Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) >> >> > >
