Re: How to FTP files to box.com

Yep, exactly what I said would happen.

IBM in their FTP client doesn't have the option to ignore the "not trusted"
(-23 for the old APIs.. funny they're not using GSKit.. odd) error. So you
have to import the CAs to "trust" the site you're FTPing to.

I'll contact you offline and see if I can get the CAs for you.

On Thu, Apr 27, 2023 at 10:50 AM mlazarus <mlazarus@xxxxxxxxxxxx> wrote:

Bradley,

I created the *SYSTEM store and got the CA authorities loaded. Now
the message says:
Secure connection error, return code -23.
-23 Certificate is not signed by a trusted certificate authority.

I'm looking at: https://www.ibm.com/support/pages/node/6610369

All the certificates are enabled. I'm still getting the error. (FTP
server was restarted.) I'm confused as to how I would assign a
certificate to the server. Is there a wizard or cookbook approach?

This process is frustrating, to say the least.

-mark

On 4/26/2023 7:14 PM, Brad Stone wrote:

First create the *SYSTEM store in DCM.

Then try again. You'll probably get a "not trusted" error. If that's

the

case you'll need to get the Certificate Authorities (CAs) from their FTP
site (openSSL can be used for this). Then import them (there may be more
than one or two in the chain) into the *SYSTEM store and you should be

good.

On Wed, Apr 26, 2023 at 3:51 PM mlazarus<mlazarus@xxxxxxxxxxxx> wrote:

Has anyone set up FTPS file transfer to FTP.BOX.COM? I would prefer
doing a secure transfer.

I'm trying: FTP RMTSYS(FTP.BOX.COM) PORT(*SECURE).

I get a message back:
Message ID . . . . . . : TCP3D2C Severity:. . . . . . . : 10

Message . . . . : Secure connection error, return code -95.
Cause . . . . . : Secure Sockets Layer (SSL) function
SSL_Init_Application returned code -95:

-95 No keyring file was specified.

How is a keyring set up and specified?

-mark

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.