Good morning, Dave, everyone...
[B
On Fri, 20 Apr 2001, Dave Horsfall wrote:
> Well, you can start by telling us what sort of a machine has the IP
> address "202.58.243.18"...
This, of course, brings up another issue entirely, one that I've been
meaning to take up with the[A list. This address *appears* to be within
ripe/apnic's 202. space. Most of the sniffing and outright attacks I've
personally witnessed have come from within that network, to such an end
that I finally blocked nearly anyone from ripe/apnic.
What alternatives are there to sheer brute lockouts? I'd written lots of
letters, and in over five years, not one answer. I'd contacted the
registrars who, in most cases, shrugged. It's my problem.
I'm not trying to justify my actions. I'm saying there is a problem, and
network security is impacted by it.
Apologies for being off-topic somewhat, but I'd like to hear what others
are doing for this problem.
Dave
--
Dave Laird ([EMAIL PROTECTED])
The Used Kharma Lot
Web Page: http://www.kharma.net updated 3/29/2001
Musicians' Calendar: http://www.kharma.net/calendar.html
Usenet news server : news://news.kharma.net
Fortune Cookie:
Let's remind ourselves that last year's fresh idea is today's cliche.
-- Austen Briggs
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
