Re: Secure connection error, return code 6000 (FTP)

[Brad Stone <bvstone@xxxxxxxxx>]

Well, the switch exists in the GSKit APIs.

If I had to show all my customers how to upload CAs every time there was an
error caused by this, I wouldn't ever get any sleep.  Even with the
instructions in the my FAQ (which have been there for years and no one
seems to look at) it still seems most need a lot of hand holding... for
this and for basic operations stuff.

Of course, I could bill for the time.  But it's one of those things that
should be easier to do.   That's the point.  With everything using the
"cloud" a simple task can become furstrating for shops that have no clue
what's going on.  They just want it to work.

On Tue, Mar 31, 2026 at 11:05 AM Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> Brad --
>
> I'm on CAAC and I find it very hard to support IDEAs that say, in effect,
> "Give me a switch to reduce security on my enterprise server, please."
> Which both alternatives suggest, though updating certs is likely to get
> easier in future updates to IBM i.
> Let's move ahead with our armor buckled on into the very hostile and
> poisonous TCP/IP environment of this turbulent decade.
>
> ________________________________
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
> Brad Stone <bvstone@xxxxxxxxx>
> Sent: Tuesday, March 31, 2026 10:00
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: Secure connection error, return code 6000 (FTP)
>
> You understand, Jack.  We're just complaining there isn't an easier way...
> either auto import of CAs or a flag you can set to say "ignore not trusted
> errors".
>
>
>
> Jack WoehrIndependent Consulting Programmer 303-847-8442
> jack.woehr@xxxxxxxxxxx www.procern.com Stay Connected!Upgrade your IT
> state of mind!NON-DISCLOSURE NOTICE: This communication including any and
> all attachments is for the intended recipient(s) only and may contain
> confidential and privileged information. If you are not the intended
> recipient of this communication, any disclosure, copying further
> distribution or use of this communication is prohibited. If you received
> this communication in error, please contact the sender and delete/destroy
> all copies of this communication immediately.
> --
> 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.