Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    Yes, TLS 1.1 is not ok. It has not been allowed for PCI DSS, Chrome is dropping it, etc. Tell them to upgrade to TLS 1.2 at least. Can you run ssllabs.com/ssltest on their server? But the code for FTPS can be very different from code on port 443. Commented Mar 29, 2020 at 8:58
  • 1
    It's not that they do not support TLS 1.2/1.3 – They do. But it does not work. – First make sure you have the latest version of curl, as there were some TLS 1.3-specific issues. – Though I have seen the problem you have even when using the latest version of curl against ProFTPD server with TLS 1.3. I have reported the problem to the ProFTPD author already (for investigation, as this might be curl problem as well). – TLS 1.2 works (for me). Commented Mar 29, 2020 at 10:48
  • 1
    Note that a similar problem happens even with WinSCP, but WinSCP does not use TLS 1.3 unless you explicitly configure it to do so. Commented Mar 29, 2020 at 10:52
  • @MartinPrikryl, <sarcasm>Don't besmirch WinSCP. Who even are you?</sarcasm> :) I set the TLS settings for min and max version to be 1.3 and transfers still worked on the Win 10 machine. I expected it to fail in the same manner and was surprised when it didn't. Commented Mar 29, 2020 at 22:05