× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I believe June or July 2017 was a deadline for financial institutions
to update their SSL certificates to the latest and greatest.

3 customers in one week so far have been affected, but only because
they are on V7R1. The only option is to update to V7R2 or higher. 2
out of 3 say they need new hardware to update to a new OS. So not
really "free".

I would be on the lookout if you use GETURI, HTTPAPI, or any other
socket application that uses SSL to communicate with financial
institutions if you're on V7R1 or lower. It will most likely stop
working soon if it hasn't already.

The only other option I can see to do, since IBM won't install the new
ciphers, is possibly ask them to update the SSL Handshake API to allow
you to bypass the RC(-1) No Ciphers error (and others like -24
SSL_ERROR_CERT_EXPIRED which is stupid anyhow) like you can with the
not trusted handshake error.

Wishful thinking. :)


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #6: Easily send group emails with Distribution Lists

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.