Home ›
SSH on a nonstandard portSSH on a nonstandard port
Submitted by Benjamin Melançon on February 2, 2007 - 10:40pm
After trying a lot of stuff that didn't work, like ssh -2 username@example.com:6927 or #6927 and many possible and impossible permutation, and after some internet searching, Agaric Design cobbled together this for your benifit. For those of you on Windows, I think you can just type in the port number. For those of you on Linux or Unix-like systems, this may help. It is tested and approved on Mac OS X:
Edit or create a plain text config (no extension) file in the .ssh (invisible system) folder in you ~/Username/ directory.
Add the directive to use a non-standard port for connecting to your machine, for instance:
Host example.com
Port 6927
Now, with SSH set to automatically select the appropriate protocol, this will work:
ssh exampleuser@example.com
Enjoy your secure, nonstandard shelling! Or let Agaric deal with it...
After trying a lot of stuff that didn't work, like ssh -2 username@example.com:6927 or #6927 and many possible and impossible permutation, and after some internet searching, Agaric Design cobbled together this for your benifit. For those of you on Windows, I think you can just type in the port number. For those of you on Linux or Unix-like systems, this may help. It is tested and approved on Mac OS X:
Edit or create a plain text config (no extension) file in the .ssh (invisible system) folder in you ~/Username/ directory.
Add the directive to use a non-standard port for connecting to your machine, for instance:
Host example.com
Port 6927
Now, with SSH set to automatically select the appropriate protocol, this will work:
ssh exampleuser@example.com
Enjoy your secure, nonstandard shelling! Or let Agaric deal with it...
Comments
Post new comment