All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Erick Sanz" <esanz@remotedynamics.com>
To: Netfilter mailing list <netfilter@lists.netfilter.org>
Subject: RE: A simple question
Date: Thu, 19 Aug 2004 10:46:06 -0500	[thread overview]
Message-ID: <FLECICIIDHIEIENHHOOLEEPBCEAA.esanz@remotedynamics.com> (raw)
In-Reply-To: <41241244.40804@svw.com>


Sudheer,

I like to block all outgoing traffic in case that someone can take control
either from my firewall system or any other system in my network.

The firewall should be the most secure system in your network; however, like
any other system, it is still vulnerable to bugs and exploits.

If the firewall allows everything out, your system can turn out to be the
one used to attack other systems. It might bee too paranoid, but I like to
protect other people from having my systems attacking theirs.

Also, if you don't have a good system security policy, you might not realize
that your system was taken over until the gentleman with the nice black
suits
knock at your door  ....    =)

-- Just my two cents! maybe even less!




> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Sudheer
> Divakaran
> Sent: Wednesday, August 18, 2004 9:37 PM
> To: Netfilter mailing list
> Subject: A simple question
>
>
> Hi,
>
> In almost all IP Tables articles I've found that the default policy of
> all tables (INPUT,OUTPUT,FORWARD) set to DROP.  I can understand it as
> far as INPUT and FORWARD tables are concerned, but I do not understand
> why should we set the default policy of OUTPUT chain to DROP.  OUTPUT
> chain is responsible for packets originating from the firewall itself.
> Whay should we DROP it?
>
> Thanks,
> Sudheer
>
>
>
> This email message has been scanned for viruses.
>



This email message has been scanned for viruses.



  parent reply	other threads:[~2004-08-19 15:46 UTC|newest]

Thread overview: 29+ 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
2004-08-19  4:52 ` Dhananjoy Chowdhury
2004-08-19 15:46 ` Erick Sanz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-17 16:24 Ajit K Jena
2011-01-17 16:32 ` Michiel Muhlenbaumer
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
2003-07-12 15:20 Performance difference between two raid0 arrays on same drives? Gordon Henderson
2003-07-16 18:11 ` A simple question Donghui Wen
2003-06-27  8:56 A Simple question Jad Saklawi
2003-06-27  9:32 ` Glynn Clements
2003-06-27 17:57 ` chuckw
2002-08-09  1:26 A simple question ed Wang
2002-08-09 16:57 ` David Love
2001-05-07 15:29 Hai Xu
2001-05-07 15:34 ` Robert M. Love
2001-05-07 15:43 ` Feng Xian

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=FLECICIIDHIEIENHHOOLEEPBCEAA.esanz@remotedynamics.com \
    --to=esanz@remotedynamics.com \
    --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.