mscdex
mscdex
Either someone is trying to MITM your connection or the server is actually providing a self-signed certificate. If it's the latter, you will need to make sure the certificate's CA...
Can you try the master branch?
I meant the master branch for *this* module (`xxhash`).
Which version of `ssh2-streams` is being used here (`npm ls` should tell you)? I just recently published a version that should have fixed this.
I can't reproduce the issue with latest `ssh2`/`ssh2-streams` with the configurations you mentioned and with a file of the same exact size. The sha1sums always match on both sides.
I don't know what their underlying platform is, so the best I'm able to do is use hpn14v11 with OpenSSH v7.3 (the only OpenSSH version that particular hpn version was...
Also, as far as transfer speed goes, `ssh2` isn't usually dramatically far off in comparison to standard OpenSSH sftp transfer using the same cipher/mac selection. For `ssh2` you can get...
You could also set `debug: console.log` and compare the resulting output between one of the servers that transfers ok and the problematic server and see if there are any obvious...
I think for behavior like this, you're better off using custom authentication handling since "partial success" could mean different things to different servers.
The connection was abruptly severed, possibly by the server. You can handle it by adding an `'error'` event handler on the connection object.