Your suggestion has worked, however it does not work consistently. When I first added the code below to the sample project it worked. However the next 3-4 attempts it failed (with the same error message I was getting originally), then worked once again, followed by another 3-4 failures:

I suggest that you contact the authors of the server and ask them why their server behaves in such a strange way. This is obviously a bug of the server, and spending time on workarounds is not the best idea, as it doesn't help fix the original issues.

We can do it the following way: try to connect to the server using CuteFTP application (it produces a nice log). Be sure to enable maximum logging level in it. If the connection is successful, please post the log here -- we will see what algorithms are accepted by the server.

Would you have any idea on your end what twofish-cbc maps to on your end? I see they also have twofish128-cbc which would likely map to SSH_EA_TWOFISH128 (and perhaps SSH_EA_TWOFISH128_CTR) on the ELDOS side. However, what would twofish-cbc map to? SSH_EA_TWOFISH256?

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.