[Red5] rmtps madness

Daniel Elliott danelliottster at gmail.com
Thu Mar 26 07:55:20 PST 2009


Oops, I should also add that I got that output while using the oflademo.

On Thu, Mar 26, 2009 at 10:24 AM, Daniel Elliott
<danelliottster at gmail.com> wrote:
> Hello,
>
> I am experiencing extreme frustration with my first attempt to use
> RTMPS with red5.  I am running RC2 version of red5.
>
> Here is what I have done thus far:
>
> + Created the certificate using: keytool -genkey -alias red5 -keyalg
> RSA -keysize 512 -validity 3650 -keystore keystore -keypass password
> -storepass password -dname
> "CN=192.168.1.50,OU=Red5,O=Red5,L=GI,ST=NE,C=US"
>
> I've tried several different things for the CN field.  I place this
> certificate in the red5/dist/conf directory
>
> + This is what my red.properties file in red5/dist/conf looks like (I
> have tried several different things for rtmps.host including the local
> ip of the computer.  I have also changed the port several times but am
> running this as a user so am unable to use the standard rtmps port
>
> #RTMPS
> rtmps.host=localhost
> rtmps.port=8443
> rtmps.ping_interval=5000
> rtmps.max_inactivity=60000
> rtmps.max_keep_alive_requests=-1
> rtmps.max_threads=20
> rtmps.acceptor_thread_count=2
> rtmps.processor_cache=20
> # RTMPS Keystore Password
> rtmps.keystorepass=password
>
> + This is what I get in my debug output (by adding
> -Djavax.net.debug=ssl to the start of the Java VM):
>
> ***
> found key for : red5
> chain [0] = [
> [
>  Version: V3
>  Subject: CN=192.168.1.50, OU=Red5, O=Red5, L=GI, ST=NE, C=US
>  Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
>
>  Key:  Sun RSA public key, 512 bits
>  modulus: 6743811056441367511233793675791490844369449088160257293522776826042030424563463598210169916390271855162577381579960697615404484479805948956441974127207639
>  public exponent: 65537
>  Validity: [From: Wed Mar 25 13:11:25 GMT-05:00 2009,
>               To: Sat Mar 23 13:11:25 GMT-05:00 2019]
>  Issuer: CN=192.168.1.50, OU=Red5, O=Red5, L=GI, ST=NE, C=US
>  SerialNumber: [    49ca73cd]
>
> ]
>  Algorithm: [SHA1withRSA]
>  Signature:
> 0000: 51 96 C8 72 D8 B7 FA 32   DC 4E FF 33 57 98 0E EE
> Q..r...2.N.3W...
> 0010: 07 52 86 76 77 23 5A 52   35 7E 0D 7C A4 97 47 78
> .R.vw#ZR5.....Gx
> 0020: 8D 15 68 0A BA 99 BE 43   FF EC 16 EA 9D B3 F4 1E
> ..h....C........
> 0030: 5E 85 93 20 DA FD 43 21   AD F4 6F 4C 86 EA 1A 0E  ^..
> ..C!..oL....
>
> ]
> ***
> adding as trusted cert:
>  Subject: CN=192.168.1.50, OU=Red5, O=Red5, L=GI, ST=NE, C=US
>  Issuer:  CN=192.168.1.50, OU=Red5, O=Red5, L=GI, ST=NE, C=US
>  Algorithm: RSA; Serial number: 0x49ca73cd
>  Valid from Wed Mar 25 13:11:25 GMT-05:00 2009 until Sat Mar 23
> 13:11:25 GMT-05:00 2019
>
> trigger seeding of SecureRandom
> done seeding SecureRandom
> [INFO] [main] org.apache.coyote.http11.Http11NioProtocol -
> Initializing Coyote HTTP/1.1 on http-8443
> [INFO] [main] org.red5.server.net.rtmps.TomcatRTMPSLoader - Starting
> RTMPS engine
> [INFO] [main] org.apache.coyote.http11.Http11NioProtocol - Starting
> Coyote HTTP/1.1 on http-8443
> Bootstrap complete
> Using SSLEngineImpl.
> http-8443-exec-1, READ: TLSv1 Handshake, length = 81
> *** ClientHello, TLSv1
> RandomCookie:  GMT: 1221227263 bytes = { 185, 19, 94, 244, 79, 53,
> 159, 109, 140, 94, 156, 51, 177, 76, 34, 152, 102, 136, 16, 210, 87,
> 13, 174, 175, 137, 81, 216, 25 }
> Session ID:  {}
> Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5,
> SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
> SSL_RSA_FIPS_WITH_DES_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA,
> SSL_RSA_EXPORT1024_WITH_RC4_56_SHA, SSL_RSA_E\
> XPORT1024_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5,
> SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5]
> Compression Methods:  { 0 }
> Unsupported extension server_name, [host_name: localhost]
> ***
> matching alias: red5
> %% Created:  [Session-1, SSL_RSA_WITH_RC4_128_MD5]
> *** ServerHello, TLSv1
> RandomCookie:  GMT: 1221227263 bytes = { 126, 158, 1, 107, 148, 213,
> 216, 49, 40, 112, 186, 200, 191, 136, 226, 13, 224, 114, 159, 253,
> 154, 52, 131, 110, 44, 63, 207, 207 }
> Session ID:  {73, 202, 115, 255, 64, 252, 252, 246, 83, 116, 188, 155,
> 108, 197, 187, 180, 21, 12, 25, 109, 46, 201, 179, 200, 13, 181, 9,
> 21, 216, 27, 10, 12}
> Cipher Suite: SSL_RSA_WITH_RC4_128_MD5
> Compression Method: 0
> ***
> Cipher suite:  SSL_RSA_WITH_RC4_128_MD5
> *** Certificate chain
> chain [0] = [
> [
>  Version: V3
>  Subject: CN=192.168.1.50, OU=Red5, O=Red5, L=GI, ST=NE, C=US
>  Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
>
>  Key:  Sun RSA public key, 512 bits
>  modulus: 6743811056441367511233793675791490844369449088160257293522776826042030424563463598210169916390271855162577381579960697615404484479805948956441974127207639
>  public exponent: 65537
>  Validity: [From: Wed Mar 25 13:11:25 GMT-05:00 2009,
>               To: Sat Mar 23 13:11:25 GMT-05:00 2019]
>  Issuer: CN=192.168.1.50, OU=Red5, O=Red5, L=GI, ST=NE, C=US
>  SerialNumber: [    49ca73cd]
>
> ]
>  Algorithm: [SHA1withRSA]
>  Signature:
> 0000: 51 96 C8 72 D8 B7 FA 32   DC 4E FF 33 57 98 0E EE
> Q..r...2.N.3W...
> 0010: 07 52 86 76 77 23 5A 52   35 7E 0D 7C A4 97 47 78
> .R.vw#ZR5.....Gx
> 0020: 8D 15 68 0A BA 99 BE 43   FF EC 16 EA 9D B3 F4 1E
> ..h....C........
> 0030: 5E 85 93 20 DA FD 43 21   AD F4 6F 4C 86 EA 1A 0E  ^..
> ..C!..oL....
>
> ]
> ***
> *** ServerHelloDone
> http-8443-exec-1, WRITE: TLSv1 Handshake, length = 518
> http-8443-exec-1, READ: TLSv1 Alert, length = 2
> http-8443-exec-1, RECV TLSv1 ALERT:  fatal, bad_certificate
> http-8443-exec-1, fatal: engine already closed.  Rethrowing
> javax.net.ssl.SSLException: Received fatal alert: bad_certificate
> http-8443-exec-1, fatal: engine already closed.  Rethrowing
> javax.net.ssl.SSLException: Received fatal alert: bad_certificate
> http-8443-exec-1, called closeOutbound()
> http-8443-exec-1, closeOutboundInternal()
> http-8443-exec-1, SEND TLSv1 ALERT:  warning, description =
> close_notify
> http-8443-exec-1, WRITE: TLSv1 Alert, length = 2
>
> I am totally at a loss now.  I've worked with this for four hours now
> and have little idea as to where to go from here.
>
> Thank you,
>
> dan
>



More information about the Red5 mailing list