Native OpenSSH performance seems quite good these days- are you certain this is still necessary? Either the SSH client and server I used had this patch, or the windowing code in SSH was removed/modified.
HPN-SSH: High Performance ssh and scp
21–30 of 32 posts
Re: HPN-SSH: High Performance ssh and scp
#22This is buggy. We had it deployed on a small number of servers , basically our backup server and a few servers that needed to backup to the backup server.
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.
Re: HPN-SSH: High Performance ssh and scp
#23check out bbcp if you are interested as well.
Do you mean bbftp? http://www.nas.nasa.gov/hecc/support/kb/bbftp_147.html
I'm guessing they meant this:
* http://pcbunn.cithep.caltech.edu/bbcp/using_bbcp.htm
* http://www.slac.stanford.edu/~abh/bbcp/
* http://www.slac.stanford.edu/~abh/bbcp/bin/
I've not tried it, though.
Re: HPN-SSH: High Performance ssh and scp
#24What is the license of these patches? There doesn’t seem to be anything on the website, nor in all of the patches available for download. 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 lic…
I wrote an email to the HPC-SSH team and got the following response:
> 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.
> Chris
Re: HPN-SSH: High Performance ssh and scp
#25After finding that using scp to copy stuff over my local network (and before finding out about hpn-ssh) I wrote this icky script to get better performance copying moving stuff around: https://github.com/toofar/fcp
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.
Re: HPN-SSH: High Performance ssh and scp
#26After finding that using scp to copy stuff over my local network (and before finding out about hpn-ssh) I wrote this icky script to get better performance copying moving stuff around: https://github.com/toofar/fcp 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 m…
no need of netcat: tar c . | ssh user@host tar x -C destdir
Re: HPN-SSH: High Performance ssh and scp
#27After finding that using scp to copy stuff over my local network (and before finding out about hpn-ssh) I wrote this icky script to get better performance copying moving stuff around: https://github.com/toofar/fcp 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 m…
no need of netcat: tar c . | ssh user@host tar x -C destdir
The need to use netcat is that it is faster. It gets better throughput in the presence of plentiful bandwidth. The whole point was to avoid using ssh for bulk transport.
Re: HPN-SSH: High Performance ssh and scp
#28Earlier quoted context omitted.
no need of netcat: tar c . | ssh user@host tar x -C destdir
The need to use netcat is that it is faster. It gets better throughput in the presence of plentiful bandwidth. The whole point was to avoid using ssh for bulk transport.
ssh user@host "nc -l 1234 | tar x -C dest_dir"
and in another terminal:
tar c . | nc -p host 1234
If you do not care about security, why not using rcp ?
Re: HPN-SSH: High Performance ssh and scp
#29This is buggy. We had it deployed on a small number of servers , basically our backup server and a few servers that needed to backup to the backup server. 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.
Could you tell me what sort of problems you were experiencing? I'm more than happy to take bug reports at hpn-ssh@psc.edu.
Re: HPN-SSH: High Performance ssh and scp
#30What is the license of these patches? There doesn’t seem to be anything on the website, nor in all of the patches available for download. 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 lic…
The Sourceforge page says the project is BSD-licensed. But if the license isn't applied to all the files, and no other root-directory file says that all the files contained within are licensed as such, i'm pretty sure you're not legally covered. If I were a distro I wouldn't include these without asking the authors to put a license declaration covering all the patch changes at the beginning of the file.
I am the author. Honestly, I initially released them without any sort of license - entirely free from any sort of license restriction. People don't seem to understand that so I said they have a BSD license on them. Personally, the license is kind of a moot point (in my view) as the once you patch OpenSSH with them the code is subsumed by the license used by OpenSSH. The only but that might be up in the air is the aes-ctr cipher. In any case I'm trying to find the cycles to include the license and then incorporate it into all of the bits and then build new packages for sourceforge. In the mean time, take my word (as the author) regarding the license. It's free and open. Just keep the attribution. Send me mail at hpn-ssh@psc.edu for identity confirmation if you like.