Re: Re: Re: Secure FTP (FTPS) battle when moving to V7R4 -- MIDRANGE-L

We have asked about the port and they confirmed it is correct. It's one of the first things we considered.

We cannot even get an appearance of a connection on 990 but of course that may be due to the new firewall.

I'm kind of in a holding pattern until the firewall people get back. It's totally possible that it's as simple as moving to 990, the vendor doesn't really know that and the firewall is blocking 990.

On 2/18/2020 10:59 AM, B Stone wrote:

So, you've double checked the port you're trying to connect to? I seem to
recall your original post using 21 which normally isn't FTPS.

I've made that mistake a few times and as I've said, that's the only time
I've ever seen the RC -16.

Good luck!

Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #17 <https://www.bvstools.com/mailtool.html>: Compatible
with Google/Gmail/G Suite, Outlook.com, Microsoft Office 365 as well as
most other SMTP servers and relays. No tricks, gimmicks or relays needed.
MAILTOOL is set up just like a PC or mobile device with the appropriate
outgoing mail router information and well as the proper authentication.

On Tue, Feb 18, 2020 at 11:56 AM Troy Hyde <troy.hyde@xxxxxxxxxxx> wrote:

Thanks for asking.

I had to leave early on Friday and am just getting back to this.

I've got some people verifying things with the vendor and also, new
information that the firewall was replaced at the same time the server
was replaced is coming to light.

As soon as I have new information, either success or more questions,
I'll post.

On 2/17/2020 6:45 AM, B Stone wrote:

Troy, any word on this?

On Fri, Feb 14, 2020 at 12:04 PM B Stone <bvstone@xxxxxxxxx> wrote:

I've only ever seen -16 when the wrong port is used trying to connect to
an SSL/TLS system.

For example, if you try to use SSL to connect to port 80 on a web site,
that is the error you will get.

Seems FTP client is using the old IBM SSL APIs as well. According to

IBM

they are legacy and don't support SNI either.

On Fri, Feb 14, 2020 at 11:40 AM Troy Hyde <troy.hyde@xxxxxxxxxxx>

wrote:

Thanks Stefan & Justin but I think/hope we've gotten beyond the cipher
suite part.

A trace on the server side's connection indicates that they are seeing

the

cipher negotiation and accepting a cipher.

We're fighting the -16 (peer system is not recognized) issue right now.

---------- Forwarded message ----------
From: Stefan Tageson <Stefan.Tageson@xxxxxxxx>
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxxxxxxxx>

Cc:
Bcc:
Date: Fri, 14 Feb 2020 14:17:17 +0000
Subject: RE: Secure FTP (FTPS) battle when moving to V7R4
Hi,
This is how it looks like in an lpar not far from here 😊
V7R4:
Sequence Cipher
number Suite
0
10 *AES_128_GCM_SHA256
20 *AES_256_GCM_SHA384
30 *CHACHA20_POLY1305_SHA256
40 *ECDHE_ECDSA_AES_128_GCM_SHA256
50 *ECDHE_ECDSA_AES_256_GCM_SHA384
60 *ECDHE_RSA_AES_128_GCM_SHA256
70 *ECDHE_RSA_AES_256_GCM_SHA384

The first three lines are new, the others are found in V7R3 as well.

V7R3:
0
10 *ECDHE_ECDSA_AES_128_GCM_SHA256
20 *ECDHE_ECDSA_AES_256_GCM_SHA384
30 *ECDHE_RSA_AES_128_GCM_SHA256
40 *ECDHE_RSA_AES_256_GCM_SHA384
50 *RSA_AES_128_GCM_SHA256
60 *RSA_AES_256_GCM_SHA384
70 *ECDHE_ECDSA_AES_128_CBC_SHA256
80 *ECDHE_ECDSA_AES_256_CBC_SHA384
90 *ECDHE_RSA_AES_128_CBC_SHA256
100 *ECDHE_RSA_AES_256_CBC_SHA384

From line 50 and below have not made it thru V7R4

TLS 1.0 and TLS 1.1 are disabled out of a V7R4-box.

Best regards

stefan.tageson@xxxxxxxx
M +46 732 369934

--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com