Re: Running ssh on unreserved ports

On Fri, 2011-02-18 at 16:07 -0500, Alex wrote:
I'd like to move it to a higher port to avoid the normal doorknob
rattling that occurs with ssh running on a public server.

Even with it on a different port, you'd probably want to implement some
firewalling that auto-bans an IP after few failed attempts. That stops
them from continually trying to get through.

I think there was a package called fail2ban, or something similar, that
did that automatically.

[tim@localhost ~]$ uname -r

Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.

users mailing list
To unsubscribe or change subscription options:

Relevant Pages

  • Re: Computer Misuse Act
    ... >>equivalent of asking for authorisation - the 'phone call' that came up ... If she's running an unprotected webserver on that port then yes. ... that were intended to be private - tough. ... If something is on a public server, you can't complain if the public ...
  • Re: firewall: black or white...
    ... I'm running a public server at a given port address. ... which contact that port first. ... There is no door. ...