Lance,

Check for these two PTFs.

MF60335 - The SSLv3 protocol and RC4 cipher suites should not be used due to the POODLE and Bar Mitzvah vulnerabilities.
SI57332 - Customer is unable to get 3rd party application updated to support the TLSv1.2 protocol. The need exists to make applications coded to use the default protocol use TLSv1.2 at a
system level to get around the 3rd party.

Read the cover letter and special instructions needed for SI57332.

Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lance Gillespie
Sent: Wednesday, August 26, 2015 11:46 AM
To: 'Midrange Systems Technical Discussion'
Subject: SSL and v7.1

Just applied the latest CUM (15142) and
our 5250 emulator (MochaSoft) stopped
working - the i rejected the connection attempt.

A bit of poking around discovered that the issue was SSL. We have MochaSoft configured to use SSL on port 996 and this seems no longer supported.

This version of MochaSoft does not support TLS but the new one does. The problem is configuring over
500 desktops with the new version is a major job we had not planned for.

I see the new sysval QSSLPCL, but none of the values seems to allow SSLv1.

Is there something I can do to change this behavior without having modify >500 computers?

Thanks,
lance


--
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.


This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2020 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].