|
On Jul 6, 2020, at 5:40 PM, Brad Stone <bvstone@xxxxxxxxx> wrote:your
In that case it's most likely ciphers were disabled with the PTFs on
side. I've had a quite few customers have this issue with PTFs in thelast
month or two.on
And it's not always just that simple. One for example had a cipher list
their server with some obsolete ciphers that were not in my customer'slist
(my client was making requests to their server). But, at least 8 othersback
matched. It still errored out until I added that one obsolete cipher
into my list, which I didn't want to do because I didn't want tooverride
the system settings for SSL. Why? If I forget I'll have the oppositeexpired
problem with new ciphers that are added.
SSL on the IBM i has always irked me for reasons like that, and for
CAs that cause all SSL to fail whether related to the communications ornot.
and
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #1 <https://www.bvstools.com/mailtool.html>: Command
ILE Interfaces available which means easily sending email from yourwrote:
programs.
On Mon, Jul 6, 2020 at 2:54 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
to
Yup - did that Brad. they all appear OK.
This started happening after we applied a couple of group PTFs so i'm
wondering if that is part of the problem.
On Jul 6, 2020, at 3:41 PM, Brad Stone <bvstone@xxxxxxxxx> wrote:
Well, if it is anything like DCM, even an expired CA that has nothing
todo
with your communications can sometimes cause problems. You may want
certscheck out CAs as well as client and server certs.wrote:
On Mon, Jul 6, 2020 at 2:26 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx>
Thanks - that has saved me a lot of trouble as it showed that the
<Kevin@xxxxxxxxxxxxxxxxxxx>are apparently good through 2028!
Time to involve someone who knows what the heck they are doing!
Thanks again.
On Jul 6, 2020, at 2:38 PM, Kevin Bucknum
lookwrote:
https://www.sslshopper.com/certificate-decoder.html
Sorry about that. From a command line
openssl x509 -in yourcertnamehere -text -noout
or just paste the text into
On Mon, 2020-07-06 at 14:33 -0400, Jon Paris wrote:
I know _where_ they are. What I'm trying to determine is how to
toat
issuethe content of them to see the expiry date. I _think_ expiry is the
but the log messages are not explicit enough to be sure. Don;t want
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaie/rzaiemod_ibm_ssl.htm#sslappnamerenew a bunch of certs only to find that was not the problem.
config is based on this.
On Jul 6, 2020, at 1:52 PM, Kevin Bucknum <
<mailto:Kevin@xxxxxxxxxxxxxxxxxxx>
Kevin@xxxxxxxxxxxxxxxxxxx
wrote:
We are still on an older php for the few apps we have running. Our
<
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaie/rzaiemod_ibm_ssl.htm#sslappname
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaie/rzaiemod_ibm_ssl.htm#sslappname
<
<
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaie/rzaiemod_ibm_ssl.htm#sslappname
for
If you are using openssl certs. Look and see if you have an update
Zendmanagement.ca-certifcates-mozilla available in the ACS open source package
On Mon, 2020-07-06 at 13:38 -0400, Jon Paris wrote:
To the server Kevin.
When we set up 5.6 we were advised to set up a local store as per
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
<
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
<
<
https://zend18.zendesk.com/hc/en-us/articles/205679027-Add-a-trusted-certificate-authority-to-IBM-i-for-PHP-5-6
themain cert - I could not find how to configure that.
Can you share the config details for the application link to use the
On Jul 6, 2020, at 1:24 PM, Kevin Bucknum <
<mailto:
<mailto:Kevin@xxxxxxxxxxxxxxxxxxx>
Kevin@xxxxxxxxxxxxxxxxxxx
<mailto:
<mailto:Kevin@xxxxxxxxxxxxxxxxxxx>
Kevin@xxxxxxxxxxxxxxxxxxx
<mailto:Kevin@xxxxxxxxxxxxxxxxxxx>
Kevin@xxxxxxxxxxxxxxxxxxx
wrote:
Connections to the php server? Or outbound connections. If it's to
elsewhere,haveserver, at least in our case, we are using the main store. In DCM we
an application defined, and in the apache setup we use the SSLAppName
directive to point to the certificate. If it's a connection
onesuse
certsopenssl to look at the cert. Something like this:
guessing that the certs may have expired - but how do I check? For
openssl s_client -connect ibmsystemsmag.com:443
On Mon, 2020-07-06 at 13:04 -0400, Jon Paris wrote:
I have a PHP setup that has started failing SSL connections. I'm
in the main store it is easy to view them - but how do I view the
otherin
PASE used by PHP?
confidential information, belonging to the sender that is legally
Jon Paris
[
<
<https://www.medtronsoftware.com/img/MedtronMinilogo.bmp>
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp
<https://www.medtronsoftware.com/img/MedtronMinilogo.bmp>
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp
<
<https://www.medtronsoftware.com/img/MedtronMinilogo.bmp>
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp
] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
<
<https://www.medtronsoftware.com>
https://www.medtronsoftware.com
<https://www.medtronsoftware.com>
https://www.medtronsoftware.com
<
<https://www.medtronsoftware.com/>
https://www.medtronsoftware.com/
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any
needparty and is required to destroy the information after its stated
employeehas
been fulfilled. If you are not the intended recipient, or the
inof
herebyagent responsible to deliver it to the intended recipient, you are
notified that any disclosure, copying, distribution or action taken
Ifreliance on the contents of these documents is STRICTLY PROHIBITED.
immediatelyyou
have received this email in error, please notify the sender
otherto
mailingarrange for return or destruction of these documents.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
list
confidential information, belonging to the sender that is legally
To post a message email:
<mailto:
<mailto:WEB400@xxxxxxxxxxxxxxxxxx>
WEB400@xxxxxxxxxxxxxxxxxx
<mailto:
<mailto:WEB400@xxxxxxxxxxxxxxxxxx>
WEB400@xxxxxxxxxxxxxxxxxx
<mailto:WEB400@xxxxxxxxxxxxxxxxxx>
WEB400@xxxxxxxxxxxxxxxxxx
<mailto:
<mailto:WEB400@xxxxxxxxxxxxxxxxxx>
WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
<
<https://lists.midrange.com/mailman/listinfo/web400>
https://lists.midrange.com/mailman/listinfo/web400
<
<https://lists.midrange.com/mailman/listinfo/web400>
https://lists.midrange.com/mailman/listinfo/web400
<https://lists.midrange.com/mailman/listinfo/web400>
https://lists.midrange.com/mailman/listinfo/web400
<
<https://lists.midrange.com/mailman/listinfo/web400>
https://lists.midrange.com/mailman/listinfo/web400
or email:
<mailto:
<mailto:WEB400-request@xxxxxxxxxxxxxxxxxx>
WEB400-request@xxxxxxxxxxxxxxxxxx
<mailto:
<mailto:WEB400-request@xxxxxxxxxxxxxxxxxx>
WEB400-request@xxxxxxxxxxxxxxxxxx
<mailto:WEB400-request@xxxxxxxxxxxxxxxxxx>
WEB400-request@xxxxxxxxxxxxxxxxxx
<mailto:
<mailto:WEB400-request@xxxxxxxxxxxxxxxxxx>
WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
<
<https://archive.midrange.com/web400>
https://archive.midrange.com/web400
<
<https://archive.midrange.com/web400>
https://archive.midrange.com/web400
<https://archive.midrange.com/web400>
https://archive.midrange.com/web400
<
<https://archive.midrange.com/web400>
https://archive.midrange.com/web400
.
[
<https://www.medtronsoftware.com/img/MedtronMinilogo.bmp>
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp
<
<https://www.medtronsoftware.com/img/MedtronMinilogo.bmp>
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp
] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
<https://www.medtronsoftware.com>
https://www.medtronsoftware.com
<
<https://www.medtronsoftware.com/>
https://www.medtronsoftware.com/
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any
needparty and is required to destroy the information after its stated
employeehas
been fulfilled. If you are not the intended recipient, or the
inof
herebyagent responsible to deliver it to the intended recipient, you are
notified that any disclosure, copying, distribution or action taken
Ifreliance on the contents of these documents is STRICTLY PROHIBITED.
immediatelyyou
have received this email in error, please notify the sender
otherto
mailingarrange for return or destruction of these documents.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
list
Bucknum
To post a message email:
<mailto:WEB400@xxxxxxxxxxxxxxxxxx>
WEB400@xxxxxxxxxxxxxxxxxx
<mailto:
<mailto:WEB400@xxxxxxxxxxxxxxxxxx>
WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
<https://lists.midrange.com/mailman/listinfo/web400>
https://lists.midrange.com/mailman/listinfo/web400
<
<https://lists.midrange.com/mailman/listinfo/web400>
https://lists.midrange.com/mailman/listinfo/web400
or email:
<mailto:WEB400-request@xxxxxxxxxxxxxxxxxx>
WEB400-request@xxxxxxxxxxxxxxxxxx
<mailto:
<mailto:WEB400-request@xxxxxxxxxxxxxxxxxx>
WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
<https://archive.midrange.com/web400>
https://archive.midrange.com/web400
<
<https://archive.midrange.com/web400>
https://archive.midrange.com/web400
.
[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin
Senior Programmer Analystconfidential information, belonging to the sender that is legally
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any
needparty and is required to destroy the information after its stated
employeehas
been fulfilled. If you are not the intended recipient, or the
inof
herebyagent responsible to deliver it to the intended recipient, you are
notified that any disclosure, copying, distribution or action taken
Ifreliance on the contents of these documents is STRICTLY PROHIBITED.
immediatelyyou
have received this email in error, please notify the sender
mailingto
mailingarrange for return or destruction of these documents.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
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.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailinglist--
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.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailinglist
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.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
listlist--
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.
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
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.