David C. Rankin schreef:
David C. Rankin wrote: (snip)
ssh -p 5129 you@your.host.com
Then all I had to do was update all my ssh aliases in .bashrc and the fact that ssh is now on a different port is completely transparent. Of course you have to change the port in you router as well. One show stopper for me would have been if the change caused difficulties with fish:// However, fish works just fine. All you need to do is add ':portnumber' to the end of the hostname like:
fish://user@somehost.com:port/
or to eliminate the password promt (if your not using public/private keys)
fish://user:pass@somehost.com:port/
Thanks for your help again Brian
Additional Information for rsync:
For rsync to work with the alternate port, you must enclose the ssh command and desired port number in single quotes. Example:
rsync -av -e 'ssh -p 5129' yoursite.com:~/tmp/somefile.doc tmp/
Works like a champ.
And scp insists on a capital P for some reason: scp -P 5129 LOCAL_FILE REMOTE_FILE -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org