From: Stephen Frost <sfrost@snowman.net>
To: netfilter@lists.netfilter.org
Subject: Re: Preventing port scanning
Date: Wed, 7 Apr 2004 15:28:03 -0400 [thread overview]
Message-ID: <20040407192803.GE7060@ns.snowman.net> (raw)
In-Reply-To: <200404071957.15692.Antony@Soft-Solutions.co.uk>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
* Antony Stone (Antony@Soft-Solutions.co.uk) wrote:
> On Wednesday 07 April 2004 7:14 pm, Stuart Lamble wrote:
> (If, for some reason, you need to have some ports open for external access to
> your network, then no, you cannot prevent people from discovering this.)
>
> You might try using some sort of tarpit rules to bog down a naive port scanner
> which scans multiple ports in a short period of time, however these will have
> no effect on scanners which are only looking for a small number of ports
> (such as 21,22,23,25,53,80,110,119,143 for example).
It depends on what ports need to be open and what ports are being
scanned. Using your example above and ipt_recent, if you don't have
port 21 open and the scan starts with that then you can drop the rest of
the attempted connections. Of course, if the scanner is doing this
across a couple of hours or from many different IP addresses it gets
more difficult.
Stephen
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-07 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 18:14 Preventing port scanning Stuart Lamble
2004-04-07 18:57 ` Antony Stone
2004-04-07 19:28 ` Stephen Frost [this message]
2004-04-07 18:57 ` Rob Sterenborg
2004-04-07 19:09 ` Antony Stone
2004-04-07 19:42 ` Rob Sterenborg
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=20040407192803.GE7060@ns.snowman.net \
--to=sfrost@snowman.net \
--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.