×
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.
Your PC had the Verisign CA certificate in the client access key store by default. But you do not have the InCommon as that is not a well-known CA.
Open up the IBM key manager and see what is included by IBM as a default. (The big guys are in there.)
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Tuesday, August 08, 2017 1:03 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Certificate change broke client access
We have never touched the local PCs keystore using iKayMan in all the years that we have been doing secure telnet (SSL) with Client Access or Access Client or System i Access for Windows. We started with a Verisign certificate many years ago and have always done a new certificate from Verisign every few years as required and that cert change never before caused a problem with secure telnet and we never did anything the PC level. It always just worked. We also turned off all SSL levels and TLS 1.0 on our desktops long ago so I don't think it’s a TLS level issue with the newer certificate. We did change to 4096 from a 2048 cert when we dis this.
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
