Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Nick Drage <nickd@funkyjesus.org>
To: netfilter mailing list <netfilter@lists.netfilter.org>
Subject: Re: what filtering to do on the OUTPUT chain?
Date: Wed, 23 Oct 2002 00:26:59 +0100	[thread overview]
Message-ID: <20021023002659.C8681@funkyjesus.org> (raw)
In-Reply-To: <20021022200357.TCVO1554.mta07-svc.ntlworld.com@there>; from Antony@Soft-Solutions.co.uk on Tue, Oct 22, 2002 at 09:03:54PM +0100

On Tue, Oct 22, 2002 at 09:03:54PM +0100, Antony Stone wrote:
> On Tuesday 22 October 2002 7:57 pm, Robert P. J. Day wrote:
> 
> >   i've had a number of people tell me that, while they put a good deal
> > of thought into their INPUT filtering, they simply ACCEPT all outgoing
> > traffic since, if their input filtering is working properly, there's no
> > reason to stop outgoing packets.
> 
> There's no reason to filter outgoing packets unless you don't trust the 
> applications running on your machine.

You shouldn't trust the applications running on your machine.

> If you don't trust what's running on your machine, then you should
> probably fix more than just what netfilter allows.

Yes, but netfilter is a good start :)

-- 
FunkyJesus System Administration Team



  reply	other threads:[~2002-10-22 23:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 18:57 what filtering to do on the OUTPUT chain? Robert P. J. Day
2002-10-22 20:03 ` Antony Stone
2002-10-22 23:26   ` Nick Drage [this message]
2002-10-22 20:09 ` Cedric Blancher
2002-10-22 20:10   ` Robert P. J. Day
2002-10-22 23:21     ` Cedric Blancher
2002-10-23  9:43       ` Antony Stone
2002-10-23 10:24         ` Cedric Blancher
2002-10-24 21:31         ` Nick Drage
2002-10-24 23:06           ` Antony Stone
2002-10-22 23:31     ` Nick Drage
2002-10-23  6:51       ` 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=20021023002659.C8681@funkyjesus.org \
    --to=nickd@funkyjesus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox