Cumulus Support

Dinant

OK, unless you are getting the exception I don't think it was picking up the new file. I had a quick look this morning, I don't think MX can be made to use an updated DLL without MX being recompiled - because the public key of the assembly will change (or be removed ;) )when I compile it. :( I thin...

Dinant

Replacing the 2 files produces also an exception during the start of cumulus. Current culture: Dutch (Netherlands) Unhandled Exception: System.IO.FileLoadException: Could not load file or assembl y 'System.Net.FtpClient, Version=1.0.5281.14359, Culture=neutral, PublicKeyToken =fa4be07daa57c2b7' or o...

Dinant

I have tested the new System.Net.FTClient DLL but it doesn't work. It produces the same error. I am using .NET Framework 4.7.1.

Dinant

I have tested MX with the newer dll. TLS 1.0 is still not working. Same error.

Dinant

The version of System.Net.FtpClient.dll MX is using is 1.0.5281.14359. On the https://www.nuget.org/packages/System.Net.FtpClient/1.0.5824.34026 it says there are two newer versions. The latest version is 1.0.5824.34026. On that page there exists a Manual download link. If you download that file and...

Dinant

I'll found some info on https://archive.codeplex.com/?p=netftp under issues. Look for the item TLSv1.2 support.
Maybe TLS1.1 and TLS1.2 must be added to the SslProtocols?

Dinant

What is the name of the FTP component you using?

Dinant

My Windows 2012 R2 server is capable of using SSLv3, TLS 1.0, TLS 1.1 and TLS 1.2 only if it also enabled on the server side.
I have tested this with WinSCP.

So I think the existing version of MX (v3.0.0 build 3042) is capable of using SSLv3 and maybe TLS 1.0.

Dinant

I have an answer from my provider. Indeed they have disabled SSLv2 and SSLv3 but also TLS v1.0. So they only support TLS 1.1 and TLS 1.2. My provider uses proFTPD with the following line in the proFTPD config file: TLSProtocol TLSv1.1 TLSv1.2 Tonight I'll do a test with WinSCP if TLS 1.1 and TLS 1.2...

Dinant

steve wrote:What version of Windows are you using - 2003 as in your profile?

I am using Windows 2012 R2.
First I'll wait for my provider to answer my questions about TLS 1.0 not working.
In the meantime I've changed my profile!

Dinant

This is what i have found on the Wiki page: https://en.wikipedia.org/wiki/FTPS Explicit In explicit mode (also known as FTPES), an FTPS client must "explicitly request" security from an FTPS server and then step up to a mutually agreed encryption method. If a client does not request securi...

Dinant

I did some tests with FTPS on 2 webservers of my provider. One with SSLv2 and SSL v3 disabled and one with the original settings (all enabled). On the servers with everything enabled there are no login problems detected. On the server with SSLv2 and SSLv3 disabled I see the following results: SSL 3....

Dinant

All I can tell you is that MX is telling the ftp client code to use Explicit ftp encryption mode. According to the documentation (and the source code) Explicit=TLS, Implicit=SSL I'm not an expert in FTPS but in the meanwhile I have read some web pages about it. https://blogs.iis.net/robert_mcmurray...

Dinant

Can they explain what the problem is, as Cumulus is clearly using TLS and not SSL? This is what they told me: For security reasons SSLv2 and SSLv3 support is disabled. There is only support for TLSv1.0, 1.1 and 1.2. I did some tests with WinSCP and SSLv3 only. This is what i see in the logging of W...

Dinant

It must be using either TLS 1.0, 1.1, or 1.2, because those are the only versions which existed at the time the ftp component was written. My conclusion is that you have some other issue. Are you using active or passive ftp mode, for example? I am using passive FTP mode (Active FTP mode not checked...

Cumulus Support

Search found 96 matches

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format

Re: The handshake failed due to un unexpected packet format