From: "curby ." <curby.public@gmail.com>
To: Brent Clark <bclark@eccotours.dyndns.org>
Cc: iptables <netfilter@lists.netfilter.org>
Subject: Re: prerouting logging
Date: Wed, 27 Jul 2005 10:58:37 -0600 [thread overview]
Message-ID: <5d2f379105072709582a10c978@mail.gmail.com> (raw)
In-Reply-To: <42E79B51.1080206@eccotours.dyndns.org>
On 7/27/05, Brent Clark <bclark@eccotours.dyndns.org> wrote:
> I got tips for nmap blocking from someone on this list.
I think I'm that someone. This looks like my post in the "Defeating
NMAP Null scans (and Nessus scans)" thread.
> Im trying to log the problems that logged.
> Would anyone care to recheck my rulset, just to make to I got this right.
You might consider more informative prefixes than just "PREROUTING: ".
It's fine if some automated parser is going through and will
determine scan type by the options logged, but a human reading the log
might be helped by an indicator like "PREROUTING NULLscan: " or
something of the sort.
> P.s. If anyone knows of any other rules I can add, it would be
> greatfully be appreciated.
My original post did include a NULL scan rule, but not the ACK scan
that Jörg mentioned.
next prev parent reply other threads:[~2005-07-27 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 14:33 prerouting logging Brent Clark
2005-07-27 14:59 ` Jörg Harmuth
2005-07-27 16:58 ` curby . [this message]
2005-07-28 6:29 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d2f379105072709582a10c978@mail.gmail.com \
--to=curby.public@gmail.com \
--cc=bclark@eccotours.dyndns.org \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.