scpa file through an intermediate host (a.k.a. jump host)
The situation is the following:
A -- ssh --> B -- ssh --> C
… where A is my client machine, B is the jump host and C is the final endpoint of the copy (either source or destination depending on the direction — the other endpoint being A)
I 've used the following option from the source:
A$ scp -oProxyCommand="ssh -W %h:%p B" thefile C:destination… and as a matter of fact reversed the copy direction (e.g. I copied from system C to system A). I.e. the incantation I used was:
A$ scp -oProxyCommand = "ssh -W %h:%p username@B" username@C:/some/path/on/macine/C some/path/on/machine/A
This is the method that I can understand more intuitively.
ssh -L 1234:C:22 username@B
scp -P 1234 -pr prj/ username@localhost:/some/path
Method B has the disadvantage that it requires that you use two shells, one for the tunnel and one for the actual scp. It also requires you to manually set up and tear down the tunnel. Finally you have to guess and reserve a local available port. This method does not suffer from these three problems.
I used the method recommended in this answer without the -o 'Host remote2' part as advised in the comments to this answer.
scp -o 'ProxyCommand ssh username@B nc %h %p' someFile username@C:/some/path
I then improved upon that since modern versions of ssh have netcat-like abilities built-in and do not require nc on the intermediate host as advised in this answer. So I did:
scp -o 'ProxyCommand ssh username@B -W %h:%p' someFile username@C:/some/path… which also worked &emdash; observe that there is now a colon (:) between %h and %p which wasn't there before.
The final improvement was to use sshpass to avoid being prompted (I had setup SSH public key authentication between A and B but was unable to do so between B and C):
sshpass -f password scp -o 'ProxyCommand ssh username@B -W %h:%p' someFile username@C:/some/path