From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Firewall Script Help
Date: Mon, 8 Mar 2004 22:06:26 +0000 [thread overview]
Message-ID: <200403082206.26777.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <W7941417650321211078780481@webmail3>
On Monday 08 March 2004 9:14 pm, cldavis@speakeasy.net wrote:
> Antony:
> > >
> > > As I understand it, this means "check the flags FIN and ACK, only match
> > > if FIN is set and ACK isn't". This would match packets that only have
> > > the FIN flag set, which I am fairly sure are valid. I may need
> > > correcting on this issue, however.
> >
> > You are correct.
>
> Packets that only have the FIN flag set are valid -- but I believe would be
> taken care of by the ESTABLISHED,RELATED rule.
Yes, that's a fair point.
> The FIN FLAG rule I entered
> just in case someone decided to bombard my systems with FIN flag packets
> only... Is that an unneeded rule to protect against a DoS attack?
I'm not aware of a DoS attack using FIN flags (since no resources get used by
a system when it receives a FIN packet), however people certainly do carry
out port scans using FIN packets, and therefore I agree with you, it's
probably a sensible thing to block.
Antony.
--
Software development can be quick, high quality, or low cost.
The customer gets to pick any two out of three.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-03-08 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 21:14 Firewall Script Help cldavis
2004-03-08 22:06 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 18:47 Christopher Davis
2004-03-08 18:49 ` David Cannings
2004-03-08 19:19 ` Christopher Davis
2004-03-08 20:12 ` David Cannings
2004-03-08 20:32 ` Antony Stone
2004-03-09 4:34 ` Mark E. Donaldson
2004-03-08 18:51 ` Aldo S. Lagana
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=200403082206.26777.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox