|
Ok, Im getting no where with IBM support on this so I thought I'd come here
to see if there are any ideas.
On two V7R3 machines using GETURI to make requests to an SSL site, I am
getting RC(-1) SSL_ERROR_NO_CIPHERS from the SSL_Handshake API.
I tried things with HTTPAPI and things seemed to work fine. (I believe
HTTPAPI uses GSKit).
IBM is telling me to contact the admin of the server to see why the error
is happening. ??
Here is what appears to be the error using a capture from the IBM i and
Wireshark to view it:
13.33.164.82 192.168.1.32 TLSv1.2 59 Alert (Level: Fatal, Description:
Handshake Failure)
I haven't used wireshark in a while, so I can tell if that's the remote
server or my local server (the 192.xxx system) that is issuing this error.
But it looks like the remote server is telling my system it's a handshake
error (why I have no idea).
Why that would cause the SSL_Handshake API to return NO_CIPHERS is also
unknown to me.
Any ideas?
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #16 <https://www.bvstools.com/mailtool.html>: No external
"helper" PC system required. 100% IBM i native!
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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.