Hi Brad,
I don't know much about the nuts and bolts of FreeBSD or Security, but I
resently had the same problem as you. I found that the Denyhosts port
(http://denyhosts.sourceforge.net/index.html) fixed the problem very well.
The non-standard, host.evil, set-up works best with the FreeBSD host
On Mon, 2006-02-06 at 21:23 +0100, Kristian Vaaf wrote:
> At 18:03 06.02.2006, Kevin Kinsey wrote:
> >Brad Gilmer wrote:
> >
> >>Hello all,
> >>
> >>I guess one of the banes of our existance as Sys Admins is that
> >>people are always pounding away at our systems trying to break
> >>in. Lately,
At 18:03 06.02.2006, Kevin Kinsey wrote:
Brad Gilmer wrote:
Hello all,
I guess one of the banes of our existance as Sys Admins is that
people are always pounding away at our systems trying to break
in. Lately, I have been getting hit with several hundred of the
messages below per dayin my
On 2/6/06, Brad Gilmer <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I guess one of the banes of our existance as Sys Admins is that people are
> always pounding away at our systems trying to break in. Lately, I have been
> getting hit with several hundred of the messages below per dayin my securi
On Mon, 06 Feb 2006 11:03:39 -0600
Kevin Kinsey <[EMAIL PROTECTED]> wrote:
> 1. edit /etc/ssh/sshd_config and make sure that only the right
> users and such are allowed to login, and via the right methods.
>
> 2. If the situation allows, you can wrap sshd
> via /etc/hosts.allow to onl
Brad Gilmer wrote:
Hello all,
I guess one of the banes of our existance as Sys Admins
is that people are always pounding away at our systems
trying to break in. Lately, I have been getting hit
with several hundred of the messages below per dayin my
security report output...
gilmer.org lo
