Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Patrick Schaaf <bof@bof.de>
To: Christian Seberino <seberino@spawar.navy.mil>
Cc: netfilter@lists.samba.org
Subject: Re: how is this stuff getting thru default deny iptables firewall?....
Date: Thu, 27 Jun 2002 09:28:54 +0200	[thread overview]
Message-ID: <20020627092854.B1873@oknodo.bof.de> (raw)
In-Reply-To: <20020627001418.A13910@spawar.navy.mil>; from seberino@spawar.navy.mil on Thu, Jun 27, 2002 at 12:14:18AM -0700

On Thu, Jun 27, 2002 at 12:14:18AM -0700, Christian Seberino wrote:
> > Reverse nat for replying packets is automatic, therefore replies get 
> > destination natted when they come back in.
> 
> This scares me.  So you are saying that there are "implicit" NAT
> rules for "replying packets" that are immune to iptables DROP rules?!

NO. You filter in the filter table's INPUT, OUTPUT, and FORWARD chains.
You can filter ANY packet there.

The NAT action (i.e. appropriate modification of IP addresses and ports)
is what happens automatically for the reverse direction - and that is
absolutely NECCESSARY for NAT to work. It's still up to you to filter
each packet after modifications have been applied.

> If a packet is part of an ESTABLISHED tcp connection then it
> can by pass an "SSH only" firewall?!??

If you have an indiscriminate ESTABLISHED/ACCEPT rule, and you did permit
the creation of the connection in the first place, then yes, that's the
case. It's all up to your own ruleset. A packet cannot become part of
an ESTABLISHED tcp connection if you do not permit an earlier packet
of the same connection to pass.

Please, Christian, tone down a bit, take a walk, take a deep breath,
and consider that we are not idiots. You don't yet know the full
picture, and painting your horrors onto your half-understanding
will just cause stress here, and make you progress more slowly.

Finally, please learn how to do test setups, and try out your suspicions
before whining about them publicly. It is very hard to guess from your
writing so far what exactly it is that you fear. If you progress by
first testing, you can describe your test setup here in detail, and
we can respond much more pointedly.

thanks for listening
  Patrick


  reply	other threads:[~2002-06-27  7:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-22 17:30 how is this stuff getting thru default deny iptables firewall? Christian Seberino
2002-06-22 17:38 ` Antony Stone
2002-06-23  7:13   ` Christian Seberino
2002-06-23  7:53     ` Patrick Schaaf
2002-06-27  7:21       ` Christian Seberino
2002-06-27  7:37         ` Patrick Schaaf
2002-07-09 19:08           ` Christian Seberino
2002-06-23  8:07     ` Antony Stone
2002-06-27  7:14       ` Christian Seberino
2002-06-27  7:28         ` Patrick Schaaf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-22 21:43 James T. Moore
2002-06-23  7:13 ` Christian Seberino
2002-07-09 19:43 j davis
2002-07-09 21:41 ` Christian Seberino
2002-07-09 21:43 ` Christian Seberino
     [not found]   ` <Pine.LNX.4.33.0207101903030.1723-100000@dodobirdy.nestac.com>
2002-07-10 16:34     ` Christian Seberino

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=20020627092854.B1873@oknodo.bof.de \
    --to=bof@bof.de \
    --cc=netfilter@lists.samba.org \
    --cc=seberino@spawar.navy.mil \
    /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