From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Nice ZoneAlarm that might be useful for Iptables
Date: Tue, 31 May 2005 22:16:29 -0400 [thread overview]
Message-ID: <20050601021629.GA6948@bender.817west.com> (raw)
In-Reply-To: <429D1994.8070809@linuxmail.org>
On Wed, Jun 01, 2005 at 10:12:36AM +0800, Feizhou wrote:
> I disagree. We do not have to provide a Zone Alarm clone. Its
> functionality of checking what processes can use the network though
> would be useful in providing mandatory controls on what processes get to
> talk to the outside world.
>
> Right now there is simply no such ability. Having this on say a server
> will prevent users from looking around the network if they have shell
> access or sending info/data out. Obviously only root should be able to
> see the list of process names allowed and the other conditions like uid
> and ports allowed to use by the process.
http://www.nsa.gov/selinux/
the mere act of saying something on a public mailing list doesn't make
it true.
-j
--
"Lois: What's going on?
Stewie: We're playing house.
Lois: The boy is all tied up.
Stewie: Roman Polanski's house."
--Family Guy
next prev parent reply other threads:[~2005-06-01 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 3:53 Nice ZoneAlarm that might be useful for Iptables Larry Alkoff
2005-05-31 4:33 ` Frank Gruellich
2005-05-31 18:18 ` R. DuFresne
2005-06-01 2:12 ` Feizhou
2005-06-01 2:16 ` Jason Opperisano [this message]
2005-06-01 2:37 ` Feizhou
2005-06-19 21:41 ` Nick Drage
2005-06-19 21:49 ` Jan Engelhardt
2005-06-20 5:28 ` Frank Gruellich
2005-06-20 6:47 ` David Busby
2005-05-31 5:07 ` Taylor, Grant
2005-05-31 6:42 ` Feizhou
2005-05-31 6:44 ` Taylor, Grant
2005-05-31 6:33 ` Eric Leblond
2005-06-19 21:35 ` Nick Drage
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=20050601021629.GA6948@bender.817west.com \
--to=opie@817west.com \
--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