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



This is a multiple purpose thread.

1) Is there a way to determine which one of the five methods are used in an SSL connection when IBM i is the client.
After changing the 3 SSL system values, it was discovered that these changes do not directly change an SSL client app.
I'm still researching, but I finding that we are using all of the five methods below.

http://www.ibm.com/developerworks/ibmi/library/i-system-ssl-ibmi/

Currently, MANUAL CHANGES ARE REQUIRED TO EACH APP TO ENABLE TLSv1.2
If IBM would make a change, client apps may not need to be touched.

In several cases, the client app was created using IBM I defaults, thus changing the client app is not a simple change.

One of our client apps uses the IBM I SSL_APIs, which, by default, only supports SSL_VERSION_CURRENT 0 (TLS Version 1.0 with SSL Version 3.0 and SSL Version 2.0 compatibility)
Per IBM development (Open PMR), changing the app to use TLSV12_TLSV11_TLSV10 9 (TLS Version 1.x only) would only work for V7R1, this will break at V7R2.
A previous related thread suggested changing this to 9, not recommended at this point.

SSLHandle
SSL_VERSION_CURRENT 0 (TLS Version 1.0 with SSL Version 3.0 and SSL Version 2.0 compatibility)
SSL_VERSION_2 2 (SSL Version 2.0 only)
SSL_VERSION_3 3 (SSL Version 3.0 only)
TLS_VERSION_1 4 (TLS Version 1.0 only)
TLSV1_SSLV3 5 (TLS Version 1.0 with SSL Version 3.0 compatibility)
TLS_VERSION_1_0 6 (TLS Version 1.0 only)
TLS_VERSION_1_1 7 (TLS Version 1.1 only)
TLS_VERSION_1_2 8 (TLS Version 1.2 only)
TLSV12_TLSV11_TLSV10 9 (TLS Version 1.x only)
TLSV12_TLSV11_TLSV10_SSLV3 10 (TLS Version 1.x with SSL Version 3.0 compatibility)

The client app could be using any of the below.
Secure sockets consists of the following APIs:

IBM(r) i Global Secure Toolkit (GSKit) APIs
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/apis/unix9a.htm?lang=en-us&cp=ssw_ibm_i_71

IBM i SSL_ APIs
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/apis/unix9b.htm?lang=en-us&cp=ssw_ibm_i_71

Open SSL APIs
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/apis/openssl.htm?lang=en-us&cp=ssw_ibm_i_71

IBM PASE for i shells and utilities
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzalf/rzalfpasecommands.htm?lang=en

Secure Sockets Layer and Java Secure Socket Extension
http://www.oracle.com/technetwork/java/index.html


2) A DCR was suggested. Before I submit one, I would like some feedback from the group, and possibly others requesting a similar change.
One option is to have SSL_VERSION_CURRENT also include TLSv1.1 and TLSv1.2. This would allow any client app to work without any changes, without breaking any clients still using V3.0 or V2.0.
Another option, if possible, was to have both the GSkit and SSL API, that if the SSL protocol was null, it would then look and use system default value QSSLPCL

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/



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.