All of lore.kernel.org
 help / color / mirror / Atom feed
From: Blizzards <blizzards@libero.it>
To: Dade <mailing@cantine.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: DROP Fin Scan
Date: Thu, 12 Dec 2002 16:25:28 +0100	[thread overview]
Message-ID: <3DF8AA68.3040900@libero.it> (raw)
In-Reply-To: 1039703255.3df89cd74ff10@zigzag.cantine.org

The idea behind the FIN scan, is not based on a NEW connection  (only 
pachet with the SYN bit set and ACK,RST,FIN cleared can initiate a new 
connection), but in sending an RST/FIN to a server to probe ports.
Closed ports reply to this CLEAR CONNECT FIN bit set packet with a RST 
bit set, while open port must ignore
the packet (this works on a unix TCP/IP stack).
FIN bits is sended by the client to server
server reply with ack
client close connect and reply with ack
server now send FIN and close connection
client receive final FIN and close all.
RST bit set produce an immediate closing of connection on both side.
In my opinion the 1st rule is exact:

iptables -A INPUT -p tcp --tcp-flags FIN,SYN FIN,SYN -j DROP

Bye.
G.




>: 
>
>Hi, 
>I'd like to block all FIN SCAN type. In Internet I find the following method: 
>
>iptables -A INPUT -p tcp --tcp-flags FIN,SYN FIN,SYN -j DROP 
>
>but for me is better to write: 
>
>iptables -A FORWARD -m state -state NEW -p tcp --tcp-flags FIN FIN -j DROP 
>
>that means blocking all packets with flag FIN active regarding only packets 
>belonging to new TCP connections. 
>Are you agree? 
>Thanks in advance, 
>Davide
>  
>




  reply	other threads:[~2002-12-12 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021124093933.24186.71076.Mailman@kashyyyk>
2002-12-12 14:27 ` DROP Fin Scan Dade
2002-12-12 15:25   ` Blizzards [this message]
2002-12-12 16:31     ` Cedric Blancher

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=3DF8AA68.3040900@libero.it \
    --to=blizzards@libero.it \
    --cc=mailing@cantine.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.