All of lore.kernel.org
 help / color / mirror / Atom feed
From: Torsten Luettgert <t.luettgert@pressestimmen.de>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Subject: Re: [LARTC] Interesting article about punching holes in firewalls...
Date: Mon, 25 Dec 2006 22:43:05 +0100	[thread overview]
Message-ID: <1167082986.2358.9.camel@elida.cbxnet.de> (raw)
In-Reply-To: <458A3E69.50600@gmx.net>

On Do, 2006-12-21 at 08:57 +0100, Carl-Daniel Hailfinger wrote:
> Grant Taylor wrote:
> > I ran across an interesting article
[...]
> This is wrong on so many levels. Please reread the article. Then read
> the source code of your favourite firewalling system. All of those
> "attacks" require cooperation from your side. And if you (or someone
> using the computer you try to protect) are actively cooperating with
> the attacker, "fixing" the firewall should be the least important of
> your problems.

Very true... the described method isn't an "attack", it's just a way to
facilitate connections between two NATed partners.

> I'm still seeing people who absolutely want to deploy the iptables
> UNCLEAN match to "make their network more secure".

This makes me curious: wouldn't UNCLEAN improve security? Afair, the
main argument against UNCLEAN (and grounds for its removal) was that
it broke ECN at some time in the past, and that "something like this
could happen again".

Personally, I like the idea of rejecting anything that violates the
existing standards.

Regards,
Torsten




  reply	other threads:[~2006-12-25 21:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  2:51 [LARTC] Interesting article about punching holes in firewalls Grant Taylor
2006-12-18  2:51 ` Grant Taylor
2006-12-18  7:26 ` Cedric Blancher
2006-12-19  9:42   ` Martijn Lievaart
2006-12-19 11:05     ` Cedric Blancher
2006-12-19 18:53       ` Martijn Lievaart
2006-12-20  3:42         ` Cedric Blancher
2006-12-19 11:07     ` Jozsef Kadlecsik
2006-12-19 11:46       ` Pascal Hambourg
2006-12-18 22:34 ` Martijn Lievaart
2006-12-18 22:50 ` Pascal Hambourg
2006-12-20 21:23 ` [LARTC] " Stephen Hemminger
2006-12-20 21:23   ` Stephen Hemminger
2006-12-21  7:10 ` [LARTC] " Peter Surda
2006-12-21  7:57 ` Carl-Daniel Hailfinger
2006-12-21  7:57   ` Carl-Daniel Hailfinger
2006-12-25 21:43   ` Torsten Luettgert [this message]
2006-12-21 15:37 ` [LARTC] " Grant Taylor
2006-12-21 15:55 ` /dev/rob0

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=1167082986.2358.9.camel@elida.cbxnet.de \
    --to=t.luettgert@pressestimmen.de \
    --cc=c-d.hailfinger.devel.2006@gmx.net \
    --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.