Fail2Ban or SSHGuard and brute-force prevention

however I have a question regarding the utilization of the /etc/hosts.deny file . . .now "depreciated"?
Access control using hosts_access(3) was created somewhere in the early 1990's when host based firewalls weren't that common. Applications need to specifically have support for it built-in or it won't work. Nowadays it's easier to create the access controls using the host's firewall as it works directly on the network layer. Applications don't have to specifically support it. So its use is largely deprecated.

Running FreeBSD 10.1-RELEASE ...will there be problems with the OS recognizing the file.
Nope, it should work. But the application you're protecting does need to have support for it. Not everything does. Sentry does look like it supports PF, so I suggest using that instead of a hosts.deny.
 
. . .already fixed it :oops:

Just so my questions on the previous page don't get lost, this URL:
https://forums.freebsd.org/threads/...and-brute-force-prevention.44255/#post-290340

A bit late on the response....

I'd keep with the default installation path in /var/db/sentry.

hosts.allow is now combined per comments in /etc/hosts.allow:

Code:
# NOTE: The hosts.deny file is deprecated.
#       Place both 'allow' and 'deny' rules in the hosts.allow file.
#       See hosts_options(5) for the format of this file.
#       hosts_access(5) no longer fully applies.

hosts.deny is specified by the following /etc/hosts.allow CONFIG lines:

Code:
sshd : /var/db/sentry/hosts.deny : deny
sshd : ALL : spawn /var/db/sentry/sentry.pl -c --ip=%a : allow
 
Back
Top