Forward an external port other than 22 to your server's internal IP address port 22.
Security through obscurity does nothing but create a false sense of security. If the OP is going with your suggestion they should look into something like fail2ban, the hackers will be scanning all ports on a public IP looking for openings.
While it does little, it does fend off most script kiddies that constantly probe and prod at the common ports. It's such a simple thing to use a different port, for failure to do so you can get broken in to, flooded logs, or have trouble properly integrating fail2ban it seems silly not to change it.
What so you think the script kiddies have not caught on to the changing of the port by now incredible...
SFTP/SSH would be the best way for that. Forward an external port other than 22 to your server's internal IP address port 22. Then access from afar using your external IP address and your new non-22 port.
Dont know if this is the correct subforum to ask
I have a linux server currently offering my filesystems via ftp, stftp, afp over my local network, works great.
How can I access any of those filesystem remotely (not in my local lan)???
I use terminal sftp/ssh a lot i was wondering if there was a way to add my sftp as you would see a file server in a network, so I graphically see files and manipulate them not using terminal.
apt-get install netatalk
mount them as afp volumes.
Extra points for adding DNS records to make them visible in the Finder
http://dns-sd.org/ServerStaticSetup.html
You can use tools such as Transmit or Cyberduck. There is even a tool that will allow you to view them with Finder called sshfs. I'm not sure if sshfs works with newer versions of Mac OS X, but I recall using it a few times with 10.5.