From: Tim Gardner <timg@tpi.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org, "Gladewitz,
Robert \(FH\)" <Robert.Gladewitz@fh-heidelberg.de>
Subject: Re: patch: Port- and netscan detection for netfilter
Date: Fri, 16 Mar 2007 10:37:11 -0600 [thread overview]
Message-ID: <45FAC7B7.40806@tpi.com> (raw)
In-Reply-To: <45FABA87.4090601@trash.net>
Patrick McHardy wrote:
> Gladewitz, Robert (FH) wrote:
>> in my Master-Theses I designed a new kernel- and netfilter module for
>> detection of net- and portscans. Now, the module is tested on more then
>> 10 different firewall-installations. It's working without any problems
>> during the last 8 months.
>>
>> Your can read the documentation on
>> http://ipt-portnetscan.sourceforge.net/. There is also a possibility to
>> download all versions of Kernel- and IpTables-Patches.
>>
>> I would be pleased to see you integrated these patches into IpTables of
>> your use.
>> Looking forward to your answer
>
> Please attach patches inline so they can be read in the mail client.
>
>> +++ linux-2.6.20.2/Documentation/ipt_PORTNETSCAN.txt
>> @@ -0,0 +1,389 @@
>> +Allgemein Informationen zum Modul ipt_PORTNETSCAN
>
> Luckily I speak german :)
>
> But seriously, we already had different portscan-detection matches
> submitted, but decided against merging them since its not clear
> what the benefit of detecting scans is. It clearly doesn't improve
> security since
>
> - you can just scan slow enough not to be detected
> - you don't need to scan to crack something
>
> So all it offers is a bit of correlated information ("you were scanned
> by ..."), that can also be extracted from log-files.
>
>
Patrick,
One benefit of being able to block a port scanner is that it reduces or
stops the amount of ARP traffic that is generated. Depending on your
internal network design, lots of ARP traffic can have a significant
impact on WAN links and so on.
rtg
--
Tim Gardner timg@tpi.com www.tpi.com
OR 503-601-0234 x102 MT 406-443-5357
next prev parent reply other threads:[~2007-03-16 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 13:29 patch: Port- and netscan detection for netfilter Gladewitz, Robert (FH)
2007-03-16 15:40 ` Patrick McHardy
2007-03-16 16:37 ` Tim Gardner [this message]
2007-03-16 16:57 ` Patrick McHardy
2007-03-16 21:32 ` Jan Engelhardt
2007-03-16 22:17 ` Gladewitz, Robert (FH)
2007-03-17 0:37 ` Jan Engelhardt
2007-03-16 21:29 ` Jan Engelhardt
2007-03-16 22:29 ` AW: " Gladewitz, Robert (FH)
2007-03-19 4:59 ` Patrick McHardy
2007-03-19 13:12 ` AW: " Gladewitz, Robert (FH)
2007-03-20 16:30 ` 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=45FAC7B7.40806@tpi.com \
--to=timg@tpi.com \
--cc=Robert.Gladewitz@fh-heidelberg.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@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.