From: "Heikki Lampén" <heze@htklx2.htk.fi>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Drop vs. Reject
Date: Wed, 19 Nov 2003 17:04:30 +0000 [thread overview]
Message-ID: <marc-lartc-106927279102179@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106925951815943@msgid-missing>
Depends, if your firewall's default policy is set to DROP then you'd
want to DROP unwanted packets.
On the other hand if you allow everything and only want to block packets
to certain (maybe M$ related) ports, then DROPping them is seen by the
evil attacker scanning your network's holes. Altho REJECTing is more
polite way of doing it, DROPping is more secure. Also REJECT sends a
port unreachable ICMP back to the dropped packet's origin.
Someone correct me if I'm wrong since I'm quite new on netfilter.
Guilherme Viebig wrote:
>Some say that DROP is the ideal manner to deal with non authorized requests,
>but using DROP let the atacker know the ports which are filtered. Using
>REJECT simply add one step to all proccess, sending the reject signal back
>to the oringin.
>
>What your perspective about it?
>
>
>
>
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-11-19 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:11 [LARTC] Drop vs. Reject Guilherme Viebig
2003-11-19 16:32 ` Jorge# ./S
2003-11-19 16:50 ` Martin A. Brown
2003-11-19 17:04 ` Heikki Lampén [this message]
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=marc-lartc-106927279102179@msgid-missing \
--to=heze@htklx2.htk.fi \
--cc=lartc@vger.kernel.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.