Blocking a slow-burning SSH bruteforce
jd.bronson at hanadarko.com
Fri Jan 1 15:44:12 UTC 2010
On 1/1/10 9:19 AM, David Rawling wrote:
> 1 is out because 22 is the one port that most organisations (including
> mine) allow out of their networks for administering routers.
> 2 is unfortunately not an option (as a consultant I do work from many
> 4 - again I might have to log in any time ...
> 3 seems the best approach.
> Thanks for your thoughts, it's good to get second opinions.
I understand using/needing port 22 opened...but what another widely used
port..like for Citrix (sp?) or something? - most firewalls have those
As far as controlling login time and access, I meant something like this:
# Allow staff access and users no access
Aurora Health Care - Milwaukee WI
More information about the freebsd-questions