From: Nick Drage <nickd@metastasis.org.uk>
To: netfilter@lists.netfilter.org
Subject: Re: A simple question
Date: Thu, 19 Aug 2004 18:31:51 +0100 [thread overview]
Message-ID: <20040819173151.GD4818@metastasis.org.uk> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF567948D@alderaan.smgtec.com>
On Thu, Aug 19, 2004 at 10:14:48AM -0700, Daniel Chemko wrote:
> Hudson Delbert J Contr 61 CS/SCBN wrote:
> > this should be a basic rule of netsec 101 ...
> >
> > one should have to 'turn' on any allowed traffic out of the box.
> >
> > i.e......the firewall should not allow ANY traffic by default until
> > specifically
> > TOLD TO DO SO BY THE ADMIN.
> >
> > this is a good thing.
> Just my two cents on this:
My two pennies :)
> If your firewall is designed correctly, there shouldn't be any network
> available services running baring SSH.
If you're using IPTables as a seperate firewall then wouldn't you just
want SSHD listening on the internal interface?
> Because of this, if a hacker gets into your firewall I assume that
> 99.9999% of the time, they'll have root access. Any hacker that could
> hack into your Linux box will be able to disable any iptables rules in
> a second. Hence, blocking the OUTPUT chain on a firewall does NOT
> secure you against hackers.
You're presuming that IPTables isn't protecting a single host. If
you're using it on a desktop or a server filtering on the OUTPUT chain
gives you a huge gain in security.
--
"I think a church with a lightning rod shows a decided lack of confidence"
next prev parent reply other threads:[~2004-08-19 17:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 17:14 A simple question Daniel Chemko
2004-08-19 17:31 ` Nick Drage [this message]
-- strict thread matches above, loose matches on Subject: below --
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 15:15 Hudson Delbert J Contr 61 CS/SCBN
2004-08-19 11:04 Jason Opperisano
2004-08-19 2:36 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
2004-04-06 2:25 Gianni Pucciani
2004-04-05 22:40 ` Antony Stone
2004-04-06 13:26 ` Gianni Pucciani
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=20040819173151.GD4818@metastasis.org.uk \
--to=nickd@metastasis.org.uk \
--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