From: Chris Kuethe <chris.kuethe@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: writing rules to disallow a domain to read particular files
Date: Sun, 17 Oct 2004 11:16:22 -0600 [thread overview]
Message-ID: <91981b3e04101710165e4ec67@mail.gmail.com> (raw)
In-Reply-To: <20041017150125.GG19398@lkcl.net>
I could be way out to lunch here, but....
Jaspreet appears to work for Ensim - a maker of web hosting appliance
software. I think what he's after is trying to use the MAC features of
SELinux to provide stronger isolation between users of a hosting
appliance than the current chroot() and application leve controls will
provide. I have access to couple of ensim boxen - not a bad little
widget. It's quite exciting to hear that the suggestion that they're
trying to use SELinux for their next generation product...
CK
--
GDB has a 'break' feature; why doesn't it have 'fix' too?
--
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-10-17 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 15:21 writing rules to disallow a domain to read particular files Jaspreet Singh
2004-10-16 17:40 ` Colin Walters
2004-10-17 12:54 ` Jaspreet Singh
2004-10-17 14:14 ` Luke Kenneth Casson Leighton
2004-10-17 14:31 ` Jaspreet Singh
2004-10-17 15:01 ` Luke Kenneth Casson Leighton
2004-10-17 17:16 ` Chris Kuethe [this message]
2004-10-17 16:35 ` Colin Walters
2004-10-18 7:58 ` Jaspreet Singh
2004-10-18 13:18 ` Colin Walters
2004-10-18 15:38 ` Karl MacMillan
2004-10-18 9:41 ` Jaspreet Singh
2004-10-18 13:22 ` Stephen Smalley
2004-10-16 19:39 ` Luke Kenneth Casson Leighton
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=91981b3e04101710165e4ec67@mail.gmail.com \
--to=chris.kuethe@gmail.com \
--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.