UNC Linux Users Group

[Brian Payst <brian_payst AT unc.edu>]

You might also consider changing the port for SSH if you are going to  
open it up to the wider world. 22 gets so much traffic from attempts  
to connect to a host that I never run SSH on the standard port. I got  
tired of parsing through logs with login failures for root, jsmith,  
ajohnson, etc.
and sorting out the noise from the issues was a pain.

It should be in /etc/ssh/sshd_config, change the Port line and then  
reload sshd

Your clients then have to specify the new port number when connecting,  
but that's not too big of a deal.

Brian

Brian Payst, MS
Director of Information Technology
Division of Student Affairs
The University of North Carolina at Chapel Hill
voice: (919) 962-1469 fax: (919) 962-5241