"-23 Certificate is not signed by a trusted certificate authority."
That's what I was afraid of. I use FTPS for bank transactions and every year I have to jump thru hoops when they change their cert.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Wednesday, March 08, 2017 9:10 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: FTPS from IBM i command line
Pressing F1 on the -95 message,
then scroll down
-95 No keyring file was specified.
So I tried it from a different lpar with some keyring history...
Connecting to host ... at address ... using port 21.
220 ProFTPD 1.3.5b Server (proftpd) [...]
234 AUTH TLS successful
Secure connection error, return code -23.
-23 Certificate is not signed by a trusted certificate authority.
Picky.
I just haven't got time for this crap.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/08/2017 09:56 AM
Subject: RE: FTPS from IBM i command line
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
When I try
FTP RMTSYS(...) SECCNN(*SSL)
I get
Connecting to host ... at address ... using port 21.
220 ProFTPD 1.3.5b Server (proftpd) [...]
Secure connection error, return code -95.
Rob Berendt
midrange.com
