Mailinglist Archive: opensuse-security (605 mails)

< Previous Next >
Still dealing with Nimda
  • From: Michelangelo van Dam <michelangelo@xxxxxxxxxxx>
  • Date: Mon, 15 Oct 2001 02:21:07 +0200 (CEST)
  • Message-id: <Pine.LNX.4.21.0110150207450.17874-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear people,

We're almost a whole month later and I still get this annoying Nimda stuff
in my webserver-logs.

They all come from within the usernetwork of my ISP, but after mailing
this instance a couple of times for complaining about this, I received
their Users Licence Agreement stating that's not allowed to run any
servers at all.

But since I'm developing webbased tools for a personal project I need to
have this webserver up and running for the outside world to visit, even
people from within my ISP's usernetwork.

Is there a way to block this incoming traffic at my firewall (without
putting these IP addresses on a BlackList since they only last for about
36 hours)?

Or are there any other solutions (like the Apache::CodeRed module but then
for Nimda)???

I'm not willing to pay full licences at my ISP before this project reaches
it's productive launch.

I'm using S.u.S.E. Linux 2.7 with kernel 2.2.19, Apache Webserver 1.3.22
with mod_perl only (No PHP) on a P-75 580MB HDD and 80MB RAM.

Yours sincerely,

Michelangelo van Dam
- -- Devoted is he, who configures sendmail without the book (unknown) --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1e-SuSE (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQE7yiv9cExHpthAaugRAmxzAJ9DkNrf3hWnzk6XDHkaNujLfYxiRgCgsx7B
kgwviIImeFuJvVV0OHm+JR8=
=bveg
-----END PGP SIGNATURE-----



< Previous Next >
Follow Ups