Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Mar 2006 06:47:55 -0800
From:      Chris Maness <chris@chrismaness.com>
To:        "Daniel A." <ldrada@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: hosts.allow ?
Message-ID:  <441D6F1B.9070005@chrismaness.com>
In-Reply-To: <5ceb5d550603190128q5f3e46c3o84e4b45236df0883@mail.gmail.com>
References:  <441CA1F9.20301@chrismaness.com> <5ceb5d550603190128q5f3e46c3o84e4b45236df0883@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Daniel A. wrote:
> On 3/19/06, Chris Maness <chris@chrismaness.com> wrote:
>   
>> My denyhost script is doing it's job by adding:
>>
>> sshd: 62.149.232.105 : deny
>>
>> to the hosts.allow file, but I see that this host is still making
>> attempts to get into my box.  Is there a cron job or something that has
>> to re-read the hosts.allow file before it the IP will be blocked?
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>>
>>     
> Offtopic, but
> How did you set up denyhosts? Daemon? Cron?
>
>   
install security/denyhost

add:

# Mmonitor logfiles for suspcious activity
@reboot root /usr/local/bin/denyhosts.py --daemon -c /etc/denyhosts.cfg

to /etc/crontab

I'm still playing with hosts.allow to get it to work right.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441D6F1B.9070005>