You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Всеволод Рябоконь <sa...@mail.ru> on 2012/12/12 14:37:45 UTC

Screensharing and recording tool does not work through RTMPS

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)



Re: Re[2]: Screensharing and recording tool does not work through RTMPS

Posted by Alexei Fedotov <al...@gmail.com>.
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 <sa...@mail.ru> 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 <al...@gmail.com>:
>
> 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, Всеволод Рябоконь <sa...@mail.ru> 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)
>>
>>
>
>

Re: Screensharing and recording tool does not work through RTMPS

Posted by Alexei Fedotov <al...@gmail.com>.
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, Всеволод Рябоконь <sa...@mail.ru> 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)
>
>

Re: Re[8]: Screensharing and recording tool does not work through RTMPS

Posted by Maxim Solodovnik <so...@gmail.com>.
I can confirm there are problems with RTMPS version of Screensharing
applet. Not sure right now what is wrong :(
I'm working on it


On Fri, Dec 14, 2012 at 12:13 PM, Maxim Solodovnik <so...@gmail.com>wrote:

> can you try Revision > 1421672 ?
>
> on my machine start - stop - start was not working correctly ... now it
> should.
> Haven't tried https yet :(
>
>
> On Fri, Dec 14, 2012 at 7:29 AM, Maxim Solodovnik <so...@gmail.com>wrote:
>
>> I work as expected on my Ubuntu last night after the fix. I'll
>> doublecheck on windows today
>>  On Dec 14, 2012 6:50 AM, "seba.wagner@gmail.com" <se...@gmail.com>
>> wrote:
>>
>>> I am sorry, after doing an SVN update, starting the recording did work.
>>> Stopping somehow didn't.
>>> Same to screensharing. I could start it. I could verify locally that it
>>> works. But hitting the pause button did not stop anything.
>>> The only way to stop sharing or recording was to close the entire
>>> screensharing client.
>>>
>>> Sebastian
>>>
>>>
>>> 2012/12/14 seba.wagner@gmail.com <se...@gmail.com>
>>>
>>>> Also the regular Scrensharing does not work for me with trunk on OSX
>>>> with Java 1.7_09
>>>> I think it there is (at least one) issue with the latest RTMPClient
>>>> library of Red5.
>>>> SSL might be affected too, however if that is another, the same (or no
>>>> issue at all with SSL in latest RTMPClient) I can't say.
>>>>
>>>> Does Screensharing and Recording with latest trunk work for you Maxim?
>>>>
>>>> Sebastian
>>>>
>>>>
>>>> 2012/12/14 Vsevolod <sa...@mail.ru>
>>>>
>>>>> I am sory, but it does not work.
>>>>> As there is not new nightly build in
>>>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/,
>>>>> I used svn to get source, so I got it and compiled with ant. ()
>>>>>
>>>>> But when I try to use screensharing, if I click button "share" or
>>>>> "record" nothing happened in java application,  i have in server log
>>>>> messages, ending with (debug ssl enabled):
>>>>>
>>>>> 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
>>>>> Using SSLEngineImpl.
>>>>> Allow unsafe renegotiation: false
>>>>> Allow legacy hello messages: true
>>>>> Is initial handshake: true
>>>>> Is secure renegotiation: false
>>>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 1
>>>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 4
>>>>>
>>>>> In java console on desktop I see
>>>>>
>>>>> DEBUG 12-13 22:29:50.316 CoreScreenShare.java 24985 224
>>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [AWT-EventQueue-0]
>>>>> - captureScreenStart
>>>>>
>>>>> after about  8 seconds in java console window on desktop I see
>>>>>
>>>>> DEBUG 12-13 22:29:55.919 RTMPSScreenShare.java 30588 78
>>>>> org.apache.openmeetings.screen.webstart.RTMPSScreenShare [NioProcessor-8] -
>>>>> connection closed
>>>>> DEBUG 12-13 22:29:55.920 CoreScreenShare.java 30589 308
>>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [NioProcessor-8] -
>>>>> ScreenShare stopStream
>>>>>
>>>>> And in server log :
>>>>> 2012-12-13 19:30:33,275 [pool-11-thread-3] INFO
>>>>> o.r.s.n.r.codec.RTMPProtocolDecoder - Action userservice.refreshSession
>>>>> 2012-12-13 19:30:35,579 [Red5_Scheduler_Worker-3] WARN
>>>>> o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from
>>>>> 193.178.34.39 : 52364 to null (in: 0 out: 0), with id 9 due to long
>>>>> handshake
>>>>>
>>>>> RITE: TLSv1 Alert, length = 2
>>>>> NioProcessor-36, called closeInbound()
>>>>> NioProcessor-36, 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-36, SEND TLSv1 ALERT:  fatal, description =
>>>>> internal_errorNioProcessor-36, SEND TLSv1 ALERT:  fatal, description =
>>>>> internal_error
>>>>> NioProcessor-36, Exception sending alert: java.io.IOException: writer
>>>>> side was already closed.
>>>>> NioProcessor-36, called closeOutbound()
>>>>> NioProcessor-36, closeOutboundInternal()
>>>>>
>>>>> In OpenMeetings 2.0 reloease and last nightly build (
>>>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/)
>>>>> it works good.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> WBR
>>>>> Maxim aka solomax
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sebastian Wagner
>>>> https://twitter.com/#!/dead_lock
>>>> http://www.webbase-design.de
>>>> http://www.wagner-sebastian.com
>>>> seba.wagner@gmail.com
>>>>
>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> https://twitter.com/#!/dead_lock
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> seba.wagner@gmail.com
>>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Re: Re[8]: Screensharing and recording tool does not work through RTMPS

Posted by Maxim Solodovnik <so...@gmail.com>.
can you try Revision > 1421672 ?

on my machine start - stop - start was not working correctly ... now it
should.
Haven't tried https yet :(


On Fri, Dec 14, 2012 at 7:29 AM, Maxim Solodovnik <so...@gmail.com>wrote:

> I work as expected on my Ubuntu last night after the fix. I'll doublecheck
> on windows today
> On Dec 14, 2012 6:50 AM, "seba.wagner@gmail.com" <se...@gmail.com>
> wrote:
>
>> I am sorry, after doing an SVN update, starting the recording did work.
>> Stopping somehow didn't.
>> Same to screensharing. I could start it. I could verify locally that it
>> works. But hitting the pause button did not stop anything.
>> The only way to stop sharing or recording was to close the entire
>> screensharing client.
>>
>> Sebastian
>>
>>
>> 2012/12/14 seba.wagner@gmail.com <se...@gmail.com>
>>
>>> Also the regular Scrensharing does not work for me with trunk on OSX
>>> with Java 1.7_09
>>> I think it there is (at least one) issue with the latest RTMPClient
>>> library of Red5.
>>> SSL might be affected too, however if that is another, the same (or no
>>> issue at all with SSL in latest RTMPClient) I can't say.
>>>
>>> Does Screensharing and Recording with latest trunk work for you Maxim?
>>>
>>> Sebastian
>>>
>>>
>>> 2012/12/14 Vsevolod <sa...@mail.ru>
>>>
>>>> I am sory, but it does not work.
>>>> As there is not new nightly build in
>>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/,
>>>> I used svn to get source, so I got it and compiled with ant. ()
>>>>
>>>> But when I try to use screensharing, if I click button "share" or
>>>> "record" nothing happened in java application,  i have in server log
>>>> messages, ending with (debug ssl enabled):
>>>>
>>>> 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
>>>> Using SSLEngineImpl.
>>>> Allow unsafe renegotiation: false
>>>> Allow legacy hello messages: true
>>>> Is initial handshake: true
>>>> Is secure renegotiation: false
>>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 1
>>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 4
>>>>
>>>> In java console on desktop I see
>>>>
>>>> DEBUG 12-13 22:29:50.316 CoreScreenShare.java 24985 224
>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [AWT-EventQueue-0]
>>>> - captureScreenStart
>>>>
>>>> after about  8 seconds in java console window on desktop I see
>>>>
>>>> DEBUG 12-13 22:29:55.919 RTMPSScreenShare.java 30588 78
>>>> org.apache.openmeetings.screen.webstart.RTMPSScreenShare [NioProcessor-8] -
>>>> connection closed
>>>> DEBUG 12-13 22:29:55.920 CoreScreenShare.java 30589 308
>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [NioProcessor-8] -
>>>> ScreenShare stopStream
>>>>
>>>> And in server log :
>>>> 2012-12-13 19:30:33,275 [pool-11-thread-3] INFO
>>>> o.r.s.n.r.codec.RTMPProtocolDecoder - Action userservice.refreshSession
>>>> 2012-12-13 19:30:35,579 [Red5_Scheduler_Worker-3] WARN
>>>> o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from
>>>> 193.178.34.39 : 52364 to null (in: 0 out: 0), with id 9 due to long
>>>> handshake
>>>>
>>>> RITE: TLSv1 Alert, length = 2
>>>> NioProcessor-36, called closeInbound()
>>>> NioProcessor-36, 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-36, SEND TLSv1 ALERT:  fatal, description =
>>>> internal_errorNioProcessor-36, SEND TLSv1 ALERT:  fatal, description =
>>>> internal_error
>>>> NioProcessor-36, Exception sending alert: java.io.IOException: writer
>>>> side was already closed.
>>>> NioProcessor-36, called closeOutbound()
>>>> NioProcessor-36, closeOutboundInternal()
>>>>
>>>> In OpenMeetings 2.0 reloease and last nightly build (
>>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/)
>>>> it works good.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> https://twitter.com/#!/dead_lock
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> seba.wagner@gmail.com
>>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>


-- 
WBR
Maxim aka solomax

Re: Re[8]: Screensharing and recording tool does not work through RTMPS

Posted by Maxim Solodovnik <so...@gmail.com>.
I work as expected on my Ubuntu last night after the fix. I'll doublecheck
on windows today
On Dec 14, 2012 6:50 AM, "seba.wagner@gmail.com" <se...@gmail.com>
wrote:

> I am sorry, after doing an SVN update, starting the recording did work.
> Stopping somehow didn't.
> Same to screensharing. I could start it. I could verify locally that it
> works. But hitting the pause button did not stop anything.
> The only way to stop sharing or recording was to close the entire
> screensharing client.
>
> Sebastian
>
>
> 2012/12/14 seba.wagner@gmail.com <se...@gmail.com>
>
>> Also the regular Scrensharing does not work for me with trunk on OSX with
>> Java 1.7_09
>> I think it there is (at least one) issue with the latest RTMPClient
>> library of Red5.
>> SSL might be affected too, however if that is another, the same (or no
>> issue at all with SSL in latest RTMPClient) I can't say.
>>
>> Does Screensharing and Recording with latest trunk work for you Maxim?
>>
>> Sebastian
>>
>>
>> 2012/12/14 Vsevolod <sa...@mail.ru>
>>
>>> I am sory, but it does not work.
>>> As there is not new nightly build in
>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/,
>>> I used svn to get source, so I got it and compiled with ant. ()
>>>
>>> But when I try to use screensharing, if I click button "share" or
>>> "record" nothing happened in java application,  i have in server log
>>> messages, ending with (debug ssl enabled):
>>>
>>> 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
>>> Using SSLEngineImpl.
>>> Allow unsafe renegotiation: false
>>> Allow legacy hello messages: true
>>> Is initial handshake: true
>>> Is secure renegotiation: false
>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 1
>>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 4
>>>
>>> In java console on desktop I see
>>>
>>> DEBUG 12-13 22:29:50.316 CoreScreenShare.java 24985 224
>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [AWT-EventQueue-0]
>>> - captureScreenStart
>>>
>>> after about  8 seconds in java console window on desktop I see
>>>
>>> DEBUG 12-13 22:29:55.919 RTMPSScreenShare.java 30588 78
>>> org.apache.openmeetings.screen.webstart.RTMPSScreenShare [NioProcessor-8] -
>>> connection closed
>>> DEBUG 12-13 22:29:55.920 CoreScreenShare.java 30589 308
>>> org.apache.openmeetings.screen.webstart.CoreScreenShare [NioProcessor-8] -
>>> ScreenShare stopStream
>>>
>>> And in server log :
>>> 2012-12-13 19:30:33,275 [pool-11-thread-3] INFO
>>> o.r.s.n.r.codec.RTMPProtocolDecoder - Action userservice.refreshSession
>>> 2012-12-13 19:30:35,579 [Red5_Scheduler_Worker-3] WARN
>>> o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from
>>> 193.178.34.39 : 52364 to null (in: 0 out: 0), with id 9 due to long
>>> handshake
>>>
>>> RITE: TLSv1 Alert, length = 2
>>> NioProcessor-36, called closeInbound()
>>> NioProcessor-36, 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-36, SEND TLSv1 ALERT:  fatal, description =
>>> internal_errorNioProcessor-36, SEND TLSv1 ALERT:  fatal, description =
>>> internal_error
>>> NioProcessor-36, Exception sending alert: java.io.IOException: writer
>>> side was already closed.
>>> NioProcessor-36, called closeOutbound()
>>> NioProcessor-36, closeOutboundInternal()
>>>
>>> In OpenMeetings 2.0 reloease and last nightly build (
>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/)
>>> it works good.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>>
>>> --
>>>
>>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>

Re: Re[8]: Screensharing and recording tool does not work through RTMPS

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I am sorry, after doing an SVN update, starting the recording did work.
Stopping somehow didn't.
Same to screensharing. I could start it. I could verify locally that it
works. But hitting the pause button did not stop anything.
The only way to stop sharing or recording was to close the entire
screensharing client.

Sebastian


2012/12/14 seba.wagner@gmail.com <se...@gmail.com>

> Also the regular Scrensharing does not work for me with trunk on OSX with
> Java 1.7_09
> I think it there is (at least one) issue with the latest RTMPClient
> library of Red5.
> SSL might be affected too, however if that is another, the same (or no
> issue at all with SSL in latest RTMPClient) I can't say.
>
> Does Screensharing and Recording with latest trunk work for you Maxim?
>
> Sebastian
>
>
> 2012/12/14 Vsevolod <sa...@mail.ru>
>
>> I am sory, but it does not work.
>> As there is not new nightly build in
>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/,
>> I used svn to get source, so I got it and compiled with ant. ()
>>
>> But when I try to use screensharing, if I click button "share" or
>> "record" nothing happened in java application,  i have in server log
>> messages, ending with (debug ssl enabled):
>>
>> 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
>> Using SSLEngineImpl.
>> Allow unsafe renegotiation: false
>> Allow legacy hello messages: true
>> Is initial handshake: true
>> Is secure renegotiation: false
>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 1
>> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 4
>>
>> In java console on desktop I see
>>
>> DEBUG 12-13 22:29:50.316 CoreScreenShare.java 24985 224
>> org.apache.openmeetings.screen.webstart.CoreScreenShare [AWT-EventQueue-0]
>> - captureScreenStart
>>
>> after about  8 seconds in java console window on desktop I see
>>
>> DEBUG 12-13 22:29:55.919 RTMPSScreenShare.java 30588 78
>> org.apache.openmeetings.screen.webstart.RTMPSScreenShare [NioProcessor-8] -
>> connection closed
>> DEBUG 12-13 22:29:55.920 CoreScreenShare.java 30589 308
>> org.apache.openmeetings.screen.webstart.CoreScreenShare [NioProcessor-8] -
>> ScreenShare stopStream
>>
>> And in server log :
>> 2012-12-13 19:30:33,275 [pool-11-thread-3] INFO
>> o.r.s.n.r.codec.RTMPProtocolDecoder - Action userservice.refreshSession
>> 2012-12-13 19:30:35,579 [Red5_Scheduler_Worker-3] WARN
>> o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from
>> 193.178.34.39 : 52364 to null (in: 0 out: 0), with id 9 due to long
>> handshake
>>
>> RITE: TLSv1 Alert, length = 2
>> NioProcessor-36, called closeInbound()
>> NioProcessor-36, 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-36, SEND TLSv1 ALERT:  fatal, description =
>> internal_errorNioProcessor-36, SEND TLSv1 ALERT:  fatal, description =
>> internal_error
>> NioProcessor-36, Exception sending alert: java.io.IOException: writer
>> side was already closed.
>> NioProcessor-36, called closeOutbound()
>> NioProcessor-36, closeOutboundInternal()
>>
>> In OpenMeetings 2.0 reloease and last nightly build (
>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/)
>> it works good.
>>
>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>>
>> --
>>
>>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com

Re: Re[8]: Screensharing and recording tool does not work through RTMPS

Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Also the regular Scrensharing does not work for me with trunk on OSX with
Java 1.7_09
I think it there is (at least one) issue with the latest RTMPClient library
of Red5.
SSL might be affected too, however if that is another, the same (or no
issue at all with SSL in latest RTMPClient) I can't say.

Does Screensharing and Recording with latest trunk work for you Maxim?

Sebastian


2012/12/14 Vsevolod <sa...@mail.ru>

> I am sory, but it does not work.
> As there is not new nightly build in
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/, I
> used svn to get source, so I got it and compiled with ant. ()
>
> But when I try to use screensharing, if I click button "share" or "record"
> nothing happened in java application,  i have in server log messages,
> ending with (debug ssl enabled):
>
> 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
> Using SSLEngineImpl.
> Allow unsafe renegotiation: false
> Allow legacy hello messages: true
> Is initial handshake: true
> Is secure renegotiation: false
> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 1
> pool-11-thread-5, WRITE: TLSv1 Application Data, length = 4
>
> In java console on desktop I see
>
> DEBUG 12-13 22:29:50.316 CoreScreenShare.java 24985 224
> org.apache.openmeetings.screen.webstart.CoreScreenShare [AWT-EventQueue-0]
> - captureScreenStart
>
> after about  8 seconds in java console window on desktop I see
>
> DEBUG 12-13 22:29:55.919 RTMPSScreenShare.java 30588 78
> org.apache.openmeetings.screen.webstart.RTMPSScreenShare [NioProcessor-8] -
> connection closed
> DEBUG 12-13 22:29:55.920 CoreScreenShare.java 30589 308
> org.apache.openmeetings.screen.webstart.CoreScreenShare [NioProcessor-8] -
> ScreenShare stopStream
>
> And in server log :
> 2012-12-13 19:30:33,275 [pool-11-thread-3] INFO
> o.r.s.n.r.codec.RTMPProtocolDecoder - Action userservice.refreshSession
> 2012-12-13 19:30:35,579 [Red5_Scheduler_Worker-3] WARN
> o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from
> 193.178.34.39 : 52364 to null (in: 0 out: 0), with id 9 due to long
> handshake
>
> RITE: TLSv1 Alert, length = 2
> NioProcessor-36, called closeInbound()
> NioProcessor-36, 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-36, SEND TLSv1 ALERT:  fatal, description =
> internal_errorNioProcessor-36, SEND TLSv1 ALERT:  fatal, description =
> internal_error
> NioProcessor-36, Exception sending alert: java.io.IOException: writer side
> was already closed.
> NioProcessor-36, called closeOutbound()
> NioProcessor-36, closeOutboundInternal()
>
> In OpenMeetings 2.0 reloease and last nightly build (
> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/)
> it works good.
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
> --
>
>


-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com

Re[8]: Screensharing and recording tool does not work through RTMPS

Posted by Vsevolod <sa...@mail.ru>.
 I am sory, but it does not work.
As there is not new nightly build in  https://builds.apache.org/view/M-R/view/OpenMeetings/job/openmeetings/ , I used svn to get source, so I got it and compiled with ant. ()

But when I try to use screensharing, if I click button "share" or "record" nothing happened in java application,  i have in server log messages, ending with (debug ssl enabled): 
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
Using SSLEngineImpl.
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
pool-11-thread-5, WRITE: TLSv1 Application Data, length = 1
pool-11-thread-5, WRITE: TLSv1 Application Data, length = 4

In java console on desktop I see 
DEBUG 12-13 22:29:50.316 CoreScreenShare.java 24985 224 org.apache.openmeetings.screen.webstart.CoreScreenShare [AWT-EventQueue-0] - captureScreenStart
after about  8 seconds in java console window on desktop I see

DEBUG 12-13 22:29:55.919 RTMPSScreenShare.java 30588 78 org.apache.openmeetings.screen.webstart.RTMPSScreenShare [NioProcessor-8] - connection closed
DEBUG 12-13 22:29:55.920 CoreScreenShare.java 30589 308 org.apache.openmeetings.screen.webstart.CoreScreenShare [NioProcessor-8] - ScreenShare stopStream

And in server log :
2012-12-13 19:30:33,275 [pool-11-thread-3] INFO  o.r.s.n.r.codec.RTMPProtocolDecoder - Action userservice.refreshSession
2012-12-13 19:30:35,579 [Red5_Scheduler_Worker-3] WARN  o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from 193.178.34.39 : 52364 to null (in: 0 out: 0), with id 9 due to long handshake
RITE: TLSv1 Alert, length = 2
NioProcessor-36, called closeInbound()
NioProcessor-36, 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-36, SEND TLSv1 ALERT:  fatal, description = internal_errorNioProcessor-36, SEND TLSv1 ALERT:  fatal, description = internal_error
NioProcessor-36, Exception sending alert: java.io.IOException: writer side was already closed.
NioProcessor-36, called closeOutbound()
NioProcessor-36, closeOutboundInternal()
In OpenMeetings 2.0 reloease and last nightly build ( https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%202.0/ ) it works good.
>>
>
>
>
>-- 
>WBR
>Maxim aka solomax


-- 


Re: Re[6]: Screensharing and recording tool does not work through RTMPS

Posted by Maxim Solodovnik <so...@gmail.com>.
Hello Vsevolod,

can you recheck with the latest build revision >= 1421390?
screensharing should be fixed.


On Thu, Dec 13, 2012 at 2:51 AM, Vsevolod <sa...@mail.ru> wrote:

> How can I debug it? I am not a developer. I see only errors that I post.
> Or must I add issue in jira?
>
>
> Среда, 12 декабря 2012, 23:14 от Alexei Fedotov <alexei.fedotov@gmail.com
> >:
>
>   You may debug the problem, or try to locate the revision when screen
> sharing over rtmps stopped working.
>
>
> --
> With best regards / с наилучшими пожеланиями,
> Alexei Fedotov / Алексей Федотов,
> http://dataved.ru/
> +7 916 562 8095
>
>
> On Wed, Dec 12, 2012 at 11:10 PM, Vsevolod <sa...@mail.ru>>
> wrote:
> > tings-incubating-2.1.0.r1420479-11-12-2012_2328.tar.gz contains red5
> 1.0.0
> > Rev 4450, wich, as I understand, include patch you mentioned...
> > http://code.google.com/p/red5/source/detail?r=4386.
> > What can I do next?
>
>
>


-- 
WBR
Maxim aka solomax

Re[6]: Screensharing and recording tool does not work through RTMPS

Posted by Vsevolod <sa...@mail.ru>.
How can I debug it? I am not a developer. I see only errors that I post. Or must I add issue in jira?


Среда, 12 декабря 2012, 23:14  от Alexei Fedotov <al...@gmail.com>:
>	
>
>
	
	
>
		
		
			
>You may debug the problem, or try to locate the revision when screen
>
sharing over rtmps stopped working.
>

>

>
--
>
With best regards / с наилучшими пожеланиями,
>
Alexei Fedotov / Алексей Федотов,
>
>http://dataved.ru/
>
+7 916 562 8095
>

>

>
On Wed, Dec 12, 2012 at 11:10 PM, Vsevolod <sa...@mail.ru> wrote:
>
> tings-incubating-2.1.0.r1420479-11-12-2012_2328.tar.gz contains red5 1.0.0
>
> Rev 4450, wich, as I understand, include patch you mentioned...
>
> http://code.google.com/p/red5/source/detail?r=4386.
>
> What can I do next?
>
>			
		
		
	

	
>


Re: Re[4]: Screensharing and recording tool does not work through RTMPS

Posted by Alexei Fedotov <al...@gmail.com>.
You may debug the problem, or try to locate the revision when screen
sharing over rtmps stopped working.


--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095


On Wed, Dec 12, 2012 at 11:10 PM, Vsevolod <sa...@mail.ru> wrote:
> tings-incubating-2.1.0.r1420479-11-12-2012_2328.tar.gz contains red5 1.0.0
> Rev 4450, wich, as I understand, include patch you mentioned...
> http://code.google.com/p/red5/source/detail?r=4386.
> What can I do next?