Eclipse Community Forums: OHF

Help

Home

Home » Archived » OHF » Mesa Test 1221

Show: Today's Messages :: Show Polls :: Message Navigator

Mesa Test 1221 [message #41053]

Mon, 25 February 2008 17:21

Eclipse User

Originally posted by: charlie.babitt.gmx.at

Hallo! I'm trying to get Mesa test 1221 running and I get the following
errors:

The mesa SERVER:

SSL_accept: :before/accept initialization
SSL_accept: :error in SSLv3 read client hello B
ERROR19113:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version
number:s3_pkt.c:290

What confuses me is the logoutput of the consumer: http-8080-1, WRITE:
SSLv2 client hello message, length = 98.

Is there a way to force it to use SSLv3? Or is this the problem that the
mesa server is expecting SSLv3 and the Consumer is sending SSLv2?

From the logs of the consumer:

trustStore type is : jks
trustStore provider is :
init truststore
adding as trusted cert:
Subject: EMAILADDRESS=certificates@acme.com, CN=ACME Certificate
Factory, OU=Research Division, O=ACME Integrated Systems, L=Champaign,
ST=Illinois, C=US
Issuer: EMAILADDRESS=certificates@acme.com, CN=ACME Certificate
Factory, OU=Research Division, O=ACME Integrated Systems, L=Champaign,
ST=Illinois, C=US
Algorithm: RSA; Serial number: 0x0
Valid from Fri Sep 07 05:25:17 CEST 2007 until Sun Nov 30 04:25:17 CET
2008

adding as trusted cert:
Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
Algorithm: RSA; Serial number: 0x0
Valid from Fri Sep 07 05:25:17 CEST 2007 until Sun Nov 30 04:25:17 CET
2008

adding as trusted cert:
Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
Algorithm: RSA; Serial number: 0x0
Valid from Mon Oct 17 20:20:53 CEST 2005 until Sun Aug 13 20:20:53 CEST
2006

adding as trusted cert:
Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
Algorithm: RSA; Serial number: 0x0
Valid from Fri Sep 07 05:25:17 CEST 2007 until Sun Nov 30 04:25:17 CET
2008

adding as trusted cert:
Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR Production, O=Washington University, L=St. Louis, ST=Missouri, C=US
Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR Production, O=Washington University, L=St. Louis, ST=Missouri, C=US
Algorithm: RSA; Serial number: 0x0
Valid from Fri Sep 07 05:25:18 CEST 2007 until Sun Nov 30 04:25:18 CET
2008

adding as trusted cert:
Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR Production, O=Washington University, L=St. Louis, ST=Missouri, C=US
Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate Factory,
OU=MIR Production, O=Washington University, L=St. Louis, ST=Missouri, C=US
Algorithm: RSA; Serial number: 0x0
Valid from Fri Sep 07 05:25:18 CEST 2007 until Sun Nov 30 04:25:18 CET
2008

trigger seeding of SecureRandom
done seeding SecureRandom
http-8080-1, setSoTimeout(30000) called
http-8080-1, setSoTimeout(30000) called
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1187115210 bytes = { 86, 131, 41, 241, 183, 104, 70,
238, 177, 244, 207, 83, 68, 151, 27, 80, 235, 219, 27, 110, 39, 16, 115,
97, 173, 177, 134, 66 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA,
TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA,
SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA,
SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5,
SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA,
SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
***
[write] MD5 and SHA1 hashes: len = 73
0000: 01 00 00 45 03 01 47 C2 F1 CA 56 83 29 F1 B7 68 ...E..G...V.)..h
0010: 46 EE B1 F4 CF 53 44 97 1B 50 EB DB 1B 6E 27 10 F....SD..P...n'.
0020: 73 61 AD B1 86 42 00 00 1E 00 04 00 05 00 2F 00 sa...B......../.
0030: 33 00 32 00 0A 00 16 00 13 00 09 00 15 00 12 00 3.2.............
0040: 03 00 08 00 14 00 11 01 00 .........
http-8080-1, WRITE: TLSv1 Handshake, length = 73
[write] MD5 and SHA1 hashes: len = 98
0000: 01 03 01 00 39 00 00 00 20 00 00 04 01 00 80 00 ....9... .......
0010: 00 05 00 00 2F 00 00 33 00 00 32 00 00 0A 07 00 ..../..3..2.....
0020: C0 00 00 16 00 00 13 00 00 09 06 00 40 00 00 15 ............@...
0030: 00 00 12 00 00 03 02 00 80 00 00 08 00 00 14 00 ................
0040: 00 11 47 C2 F1 CA 56 83 29 F1 B7 68 46 EE B1 F4 ..G...V.)..hF...
0050: CF 53 44 97 1B 50 EB DB 1B 6E 27 10 73 61 AD B1 .SD..P...n'.sa..
0060: 86 42 .B
http-8080-1, WRITE: SSLv2 client hello message, length = 98
http-8080-1, handling exception: java.net.SocketException: Connection reset
http-8080-1, SEND TLSv1 ALERT: fatal, description = unexpected_message
http-8080-1, WRITE: TLSv1 Alert, length = 2
http-8080-1, Exception sending alert: java.net.SocketException: Broken pipe
http-8080-1, called closeSocket()
http-8080-1, called close()
http-8080-1, called closeInternal(true)
http-8080-1, called close()
http-8080-1, called closeInternal(true)
http-8080-1, called close()
http-8080-1, called closeInternal(true)
http-8080-1, setSoTimeout(30000) called
http-8080-1, setSoTimeout(30000) called

Report message to a moderator

Re: Mesa Test 1221 [message #41177 is a reply to message #41053]

Mon, 03 March 2008 17:33

No real name

Messages: 292
Registered: July 2009

Senior Member

Hi Patrick,

There seems to be another thing going on -
http-8080-1, handling exception: java.net.SocketException: Connection reset

do you have a firewall up?

- Sarah

Patrick wrote:
> Hallo! I'm trying to get Mesa test 1221 running and I get the following
> errors:
>
> The mesa SERVER:
>
> SSL_accept: :before/accept initialization
> SSL_accept: :error in SSLv3 read client hello B
> ERROR19113:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version
> number:s3_pkt.c:290
>
>
> What confuses me is the logoutput of the consumer: http-8080-1, WRITE:
> SSLv2 client hello message, length = 98.
>
> Is there a way to force it to use SSLv3? Or is this the problem that the
> mesa server is expecting SSLv3 and the Consumer is sending SSLv2?
>
> From the logs of the consumer:
>
> trustStore type is : jks
> trustStore provider is :
> init truststore
> adding as trusted cert:
> Subject: EMAILADDRESS=certificates@acme.com, CN=ACME Certificate
> Factory, OU=Research Division, O=ACME Integrated Systems, L=Champaign,
> ST=Illinois, C=US
> Issuer: EMAILADDRESS=certificates@acme.com, CN=ACME Certificate
> Factory, OU=Research Division, O=ACME Integrated Systems, L=Champaign,
> ST=Illinois, C=US
> Algorithm: RSA; Serial number: 0x0
> Valid from Fri Sep 07 05:25:17 CEST 2007 until Sun Nov 30 04:25:17 CET
> 2008
>
> adding as trusted cert:
> Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
> Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
> Algorithm: RSA; Serial number: 0x0
> Valid from Fri Sep 07 05:25:17 CEST 2007 until Sun Nov 30 04:25:17 CET
> 2008
>
> adding as trusted cert:
> Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
> Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
> Algorithm: RSA; Serial number: 0x0
> Valid from Mon Oct 17 20:20:53 CEST 2005 until Sun Aug 13 20:20:53 CEST
> 2006
>
> adding as trusted cert:
> Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
> Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR, O=Washington University, L=St. Louis, ST=Missouri, C=US
> Algorithm: RSA; Serial number: 0x0
> Valid from Fri Sep 07 05:25:17 CEST 2007 until Sun Nov 30 04:25:17 CET
> 2008
>
> adding as trusted cert:
> Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR Production, O=Washington University, L=St. Louis,
> ST=Missouri, C=US
> Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR Production, O=Washington University, L=St. Louis,
> ST=Missouri, C=US
> Algorithm: RSA; Serial number: 0x0
> Valid from Fri Sep 07 05:25:18 CEST 2007 until Sun Nov 30 04:25:18 CET
> 2008
>
> adding as trusted cert:
> Subject: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR Production, O=Washington University, L=St. Louis,
> ST=Missouri, C=US
> Issuer: EMAILADDRESS=mesa@wuerl.wustl.edu, CN=MESA Certificate
> Factory, OU=MIR Production, O=Washington University, L=St. Louis,
> ST=Missouri, C=US
> Algorithm: RSA; Serial number: 0x0
> Valid from Fri Sep 07 05:25:18 CEST 2007 until Sun Nov 30 04:25:18 CET
> 2008
>
> trigger seeding of SecureRandom
> done seeding SecureRandom
> http-8080-1, setSoTimeout(30000) called
> http-8080-1, setSoTimeout(30000) called
> %% No cached client session
> *** ClientHello, TLSv1
> RandomCookie: GMT: 1187115210 bytes = { 86, 131, 41, 241, 183, 104, 70,
> 238, 177, 244, 207, 83, 68, 151, 27, 80, 235, 219, 27, 110, 39, 16, 115,
> 97, 173, 177, 134, 66 }
> Session ID: {}
> Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA,
> TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
> TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA,
> SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA,
> SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA,
> SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5,
> SSL_RSA_EXPORT_WITH_DES40_CBC_SHA,
> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA,
> SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
> Compression Methods: { 0 }
> ***
> [write] MD5 and SHA1 hashes: len = 73
> 0000: 01 00 00 45 03 01 47 C2 F1 CA 56 83 29 F1 B7 68 ...E..G...V.)..h
> 0010: 46 EE B1 F4 CF 53 44 97 1B 50 EB DB 1B 6E 27 10 F....SD..P...n'.
> 0020: 73 61 AD B1 86 42 00 00 1E 00 04 00 05 00 2F 00 sa...B......../.
> 0030: 33 00 32 00 0A 00 16 00 13 00 09 00 15 00 12 00 3.2.............
> 0040: 03 00 08 00 14 00 11 01 00 .........
> http-8080-1, WRITE: TLSv1 Handshake, length = 73
> [write] MD5 and SHA1 hashes: len = 98
> 0000: 01 03 01 00 39 00 00 00 20 00 00 04 01 00 80 00 ....9... .......
> 0010: 00 05 00 00 2F 00 00 33 00 00 32 00 00 0A 07 00 ..../..3..2.....
> 0020: C0 00 00 16 00 00 13 00 00 09 06 00 40 00 00 15 ............@...
> 0030: 00 00 12 00 00 03 02 00 80 00 00 08 00 00 14 00 ................
> 0040: 00 11 47 C2 F1 CA 56 83 29 F1 B7 68 46 EE B1 F4 ..G...V.)..hF...
> 0050: CF 53 44 97 1B 50 EB DB 1B 6E 27 10 73 61 AD B1 .SD..P...n'.sa..
> 0060: 86 42 .B
> http-8080-1, WRITE: SSLv2 client hello message, length = 98
> http-8080-1, handling exception: java.net.SocketException: Connection reset
> http-8080-1, SEND TLSv1 ALERT: fatal, description = unexpected_message
> http-8080-1, WRITE: TLSv1 Alert, length = 2
> http-8080-1, Exception sending alert: java.net.SocketException: Broken pipe
> http-8080-1, called closeSocket()
> http-8080-1, called close()
> http-8080-1, called closeInternal(true)
> http-8080-1, called close()
> http-8080-1, called closeInternal(true)
> http-8080-1, called close()
> http-8080-1, called closeInternal(true)
> http-8080-1, setSoTimeout(30000) called
> http-8080-1, setSoTimeout(30000) called
>
>

Report message to a moderator

Re: Mesa Test 1221 [message #41239 is a reply to message #41177]

Thu, 06 March 2008 16:55

Eclipse User

Originally posted by: patrick.mangesius.healthatnet.at

The issue is solved, it was not a firewall problem but the usage of a
wrong cipher for initating the handshake. That caused the mesa test server
to stop communicating with the client...

Thanks for you help

Report message to a moderator

Re: Mesa Test 1221 [message #584799 is a reply to message #41053]

Mon, 03 March 2008 17:33

No real name

Messages: 292
Registered: July 2009

Senior Member

Report message to a moderator

Re: Mesa Test 1221 [message #584831 is a reply to message #41177]

Thu, 06 March 2008 16:55

Patrick

Messages: 55
Registered: July 2009

Member

The issue is solved, it was not a firewall problem but the usage of a
wrong cipher for initating the handshake. That caused the mesa test server
to stop communicating with the client...

Thanks for you help

Report message to a moderator

Previous Topic:	OHF IHE actor implementations
Next Topic:	ATNA Mesa Test Troubles

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 02:24:20 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter