On Wed, Jul 12, 2017 at 05:28:47PM -0500, Doug wrote: > > > On Wed, Jul 12, 2017 at 12:09:09PM -0500, Dave Ihnat wrote: > > > On Wed, Jul 12, 2017 at 10:55:01AM -0400, Frank Pikelner wrote: > > > > It is not complicated finding SSH running on a different port using Nmap: > > > That's true. It's also true that the vast majority of scriptkiddies don't > > > do that. Quite seriously, moving SSH off port 22 *will* and *does* drop > > > the vast majority of doorknob rattling. > > > > > > > Suggest adding something like Fail2Ban to slow down the password guess > > > > attempts against SSH. > > > True. Not only that, but also adding DenyHosts. > > > > jl > How do you move SSH off port 22? Please supply konsole code. > If you are using a router to connect to your ISP it may provide an alternative to changing the sshd configuration. The ones I've used have a feature called 'port forwarding'; if something comes in on port X forward it to host A on port Y. For example, my router forwards internet connections that come in on to port 222 to host 'mums' on port 22. Similarly, connections on port 223 are directed to host 'vost' on port 22. No change is needed in the sshd configuration so I can still use the normal port 22 for connections inside my lan. Jon -- Jon H. LaBadie jonfu@xxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
