|
Hi Paul.
What are you using to connect/communicate? Can you get the return code?
Do you know if the GSKit APIs are used or the standard SSL APIs are being
used for the connect?
I ran into an issue with a customer on V7R1 that was trying to use V7R1 and
up and the SSL APIs weren't really doing things right, so on the SSL
Handshake API we had to tell it by sending it the proper code and that
cleared things up.
Here's a link to an article I wrote about it.. it refers to GETURI but it
would also apply to any client application that uses the SSL APIs. (the
GSKit APIs may have a different setting).
http://www.fieldexit.com/forum/display?threadid=170
Brad
www.bvstools.com
On Fri, Jun 26, 2015 at 8:06 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:
I'm receiving this error when trying to connect to a remote server.
SSL_Handshake(): Peer not recognized or badly formatted message received.
V7R1, TR10, latest CUM 15142 and all groups
I've confirmed DCM has proper CA, both root and intermediate.
Remote server has TLS1.0 disabled, TLS1.2 is currently being used for
other connections to that server.
I'm thinking this is either a SSL protocol issue or cipher issue.
I know when the I is the server, the DCM application defaults need to be
changed to allow TLS1.2 , TLS1.1 and disable SSL 3.0, SSL2.0
Also cipher defaults need to be changed.
Are there similar settings for when the I is the client?
I've seen other posts with this error, but did not see the final
resolution.
- - - - - - - - - - - - - - - - - - - - - - - C O N N E C T I O N F E E
D B A C K -
About to connect() to XXXXXX-web.XXX.net port 443 (#0)
Trying XXX.XXX.XXX.X... connected
SSL_Handshake(): Peer not recognized or badly formatted message received.
Closing connection #0
SSL connect error
************End of Data********************
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.