Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Nov 2002 22:24:53 -0600
From:      "Kevin D. Kinsey, DaleCo, S.P." <kdk@daleco.biz>
To:        "Stephen Hovey" <shovey@buffnet.net>, "W. D." <WD@US-Webmasters.com>
Cc:        <freebsd-questions@FreeBSD.ORG>
Subject:   Re: How to stop SPAMMER??!
Message-ID:  <00aa01c2893a$49b06280$fa00a8c0@DaleCoportable>
References:  <5.1.0.14.2.20021110034425.04b7c9d0@us-webmasters.com> <5.1.0.14.2.20021110210555.046f49d0@us-webmasters.com>

next in thread | previous in thread | raw e-mail | index | archive | help
From: "W. D." <WD@US-Webmasters.com>
Subject: Re: How to stop SPAMMER??!


>Hi Stephen,

>I hope you don't mind, I've CC'd the list as well:

>Guys: I locked myself out of my server using the "hosts.allow"
script
>below.  I couldn't get in with SSH, FTP, and *ALL* email was
blocked.
>I changed back to the old "hosts.allow" and I can get back
>in, but so are the slimy spammers.

>It seems that "hosts.allow" is very powerfull--perhaps the way to
>go.  However, I can't shut off FTP and email for all the other
users.
>Does anyone have "ready-to-go" hosts.allow file?
>
>

Well, now we see why the file comments suggest that wrapping
sshd is *not* such a good idea......

Get the IP block of the system(s) from which you are remotely
adminning the server into hosts.allow with something like this
at the top:

all:  192.168.0.0/255.255.255.0 : allow

This is a sample netblock that makes sure hosts on my/the*
LAN have access to the machine....figure out the netblock
of your ISP at the home, office, or home office, and try,
try, again.....

HTH,

Kevin Kinsey
DaleCo, S.P.

*Your LAN may differ, of course.....



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00aa01c2893a$49b06280$fa00a8c0>