From: Torsten Luettgert <t.luettgert@pressestimmen.de>
To: netfilter@lists.netfilter.org
Subject: RE: A simple question
Date: Thu, 19 Aug 2004 10:39:44 +0200 [thread overview]
Message-ID: <1092904784.9327.11.camel@scaramouche> (raw)
In-Reply-To: <SERVER7QYx3G5aYY61L00000074@server7.bandwidthco.com>
On Don, 2004-08-19 at 06:18, Mark E. Donaldson wrote:
> As you might expect, it is quite easy to DOS the firewall itself
> when OUTPUT is set to DROP. And that is not a real good idea.
Please elaborate - why is it easy to DOS the firewall if the output
policy is DROP? You don't mean icmp/source-quench not getting
delivered or something?
> However, having said that, close scrutiny must be paid to what you
> allow out of the firewall and the necessary rules must be in place.
...which is why I personally use DROP as default policy for all
chains and explicitly allow everything I think necessary :-)
The only exception is in the mangle table, where I use ACCEPT
policies and just filter out the obvious spoofs, unclean frames
etc.
Greetings,
Torsten
next prev parent reply other threads:[~2004-08-19 8:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 2:36 A simple question Sudheer Divakaran
2004-08-19 4:18 ` Mark E. Donaldson
2004-08-19 8:39 ` Torsten Luettgert [this message]
2004-08-19 4:52 ` Dhananjoy Chowdhury
2004-08-19 15:46 ` Erick Sanz
-- strict thread matches above, loose matches on Subject: below --
2005-08-10 0:11 A Simple Question Robb Bossley
2005-08-10 19:58 ` /dev/rob0
2005-08-11 5:54 ` Jan Engelhardt
2005-08-12 5:27 ` Grant Taylor
2004-08-19 17:58 A simple question Hudson Delbert J Contr 61 CS/SCBN
2004-08-19 17:47 Daniel Chemko
2004-08-19 17:14 Daniel Chemko
2004-08-19 17:31 ` Nick Drage
2004-08-19 15:15 Hudson Delbert J Contr 61 CS/SCBN
2004-08-19 11:04 Jason Opperisano
2004-04-06 2:25 Gianni Pucciani
2004-04-05 22:40 ` Antony Stone
2004-04-06 13:26 ` Gianni Pucciani
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=1092904784.9327.11.camel@scaramouche \
--to=t.luettgert@pressestimmen.de \
--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