brew install --with-hpn https://raw.githubusercontent.com/FiloSottile/homebrew-dupes/423f9eed0e557f4a63947b04f5dbe22c895ff6f7/openssh.rb
brew tap homebrew/dupes
brew install --with-hpn openssh
We would run into problems with standard SSH connecting to HPN-SSH these bugs were confusing and difficult to debug until we realized that the difference was HPN-SSH and reverted to standard SSH all problems went away quite quickly.
Are there other reasons apart from licensing why this has not been merged into mainline OpenSSH?
Edit: At least the multithreaded AES-CTR cipher has license information in the header, which seems to be standard BSD. It stands to reason that the rest of the patches have the same license?
> I'm at a conference this week so I'll make the license more clear next week in the repo. Basically, it's a very lax bsd style license. Maintain attribution and you can do as you like with it. However, please understand that when incorporated into OpenSSH the OpenSSH license takes precedence.
> Also out had been submitted some years ago but there was resistance to the patch for non technical reasons so I've home my own way on it.
I think that it was merged into FreeBSD a while back though:
In addition to host and network tuning guides they also have a list of data transfer tools, including HPN-patched sftp and scp, but they recommend GridFTP because it supports parallel streams: http://fasterdata.es.net/data-transfer-tools/gridftp/
It just wraps ssh+netcat+tar. The ssh connection is just used to setup the netcat (actually nc) connection like in mosh.
It doesn't have much dependencies (although it can use pv if installed on the local machine) and so should work on most platforms (didn't work on android last I checked, but I think I know why). It's a pretty ugly script (in particular errors are not propagated back to the terminal and backgrounding pv can lead to offset output) but it works and can even use scp's bash_completion script for completion on a remote filesystem.
and in another terminal:
tar c . | nc -p host 1234
If you do not care about security, why not using rcp ?
(say, 300Mb+ connections with 30ms+ latency)
PSC has been maintaining these patches for a long time. I'm pretty sure I was using this nearly 10 years ago. If you have a need for this, it's not hard to build it yourself.
Ah, found the initial release date: July 7, 2004; yeah 10 years.
I've not tried it, though.