From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Erich Schubert <erich@debian.org>
Cc: russell@coker.com.au, selinux@tycho.nsa.gov
Subject: Re: Additional rule files
Date: Sun, 5 Sep 2004 18:34:52 +0100 [thread overview]
Message-ID: <20040905173452.GH4084@lkcl.net> (raw)
In-Reply-To: <1094392498.22073.19.camel@wintermute.xmldesign.de>
On Sun, Sep 05, 2004 at 03:54:58PM +0200, Erich Schubert wrote:
> Hi,
>
> > Why does fnord need a different policy? Are the actions of different web
> > servers that different? (this is a serious question not a rhetorical
> > question)
>
> Well, apache contains a lot of stuff. Fnord and tcpserver are much
> smaller applications that would allow a fine-grained definition of
> rules. (one of the reasons i don't like apache that much is that it
> contains a huge amount of stuff you usually do not use)
apache is modular: i assume that at some point the apache policy
would reflect this modularity [with tunables/apache_modules.te?]
l.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-09-05 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 1:12 Additional rule files Erich Schubert
2004-09-05 10:19 ` Russell Coker
2004-09-06 17:12 ` Erich Schubert
2004-09-13 22:52 ` Erich Schubert
2004-09-19 10:02 ` Russell Coker
2004-10-02 23:37 ` Erich Schubert
2004-09-05 10:27 ` Russell Coker
2004-09-05 10:31 ` Russell Coker
2004-09-05 13:54 ` Erich Schubert
2004-09-05 17:34 ` Luke Kenneth Casson Leighton [this message]
2004-09-05 17:38 ` Erich Schubert
2004-09-05 18:50 ` Luke Kenneth Casson Leighton
2004-09-05 10:45 ` log file names (was Additional rule files) Russell Coker
[not found] ` <00ab01c4933f$c66e32f0$0a01a8c0@huey>
2004-09-05 12:52 ` Is anyone using Selinux for VOIP applications? Russell Coker
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=20040905173452.GH4084@lkcl.net \
--to=lkcl@lkcl.net \
--cc=erich@debian.org \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
/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.