|
Nope.
still have the "ssl_error(415): (GSKit) Peer not recognized or badly
formatted message received." errors.
On Mon, Nov 9, 2020 at 10:54 AM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx>
wrote:
I just found and applied MF67905.--
DESCRIPTION OF PROBLEM FIXED FOR APAR MA48640 :
-----------------------------------------------
When a callback function is set on gsk_attribute_set_callback()
for GSK_CERT_VALIDATION_CALLBACK, TLSv1.2 cached handshakes fail
with GSK_ERROR_BAD_PEER.
CORRECTION FOR APAR MA48640 :
-----------------------------
The TLSv1.2 handshake path was updated to properly handle cached
handshakes when there is a callback function set on
gsk_attribute_set_callback() for GSK_CERT_VALIDATION_CALLBACK.
I have just applied said ptf, and will see how it goes.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
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.
midrange.com
