From: David Cary Hart <dch@TQMcube.com>
To: Tom Eastep <teastep@shorewall.net>
Cc: Ray Anderson <rsa@prideindustries.com>,
Netfilter Users' List <netfilter@lists.netfilter.org>
Subject: Re: Shorewall vs. Iptables
Date: Thu, 12 Feb 2004 17:17:17 -0500 [thread overview]
Message-ID: <1076624237.3037.26.camel@dchws.TQMcube.com> (raw)
In-Reply-To: <200402121356.56294.teastep@shorewall.net>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
On Thu, 2004-02-12 at 16:56, Tom Eastep wrote:
> My opinion is far from unbiased but here goes. Shorewall is a high-level tool
> for configuring netfilter. It uses the iptables utility to do so. As a
> result, it cannot offer any more protection than the iptables utility used
> alone can provide.
>
Correct me if I am wrong but Shorewall only works properly on a
dedicated box. In other words, if you are running netfilter on the same
machine as a server then Shorewall doesn't work properly.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-12 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 21:32 Shorewall vs. Iptables Ray Anderson
2004-02-12 21:56 ` Tom Eastep
2004-02-12 22:17 ` David Cary Hart [this message]
2004-02-12 22:21 ` Tom Eastep
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=1076624237.3037.26.camel@dchws.TQMcube.com \
--to=dch@tqmcube.com \
--cc=netfilter@lists.netfilter.org \
--cc=rsa@prideindustries.com \
--cc=teastep@shorewall.net \
/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