From: Richard Hally <rhally@mindspring.com>
To: russell@coker.com.au
Cc: Joshua Brindle <method@gentoo.org>,
KaiGai Kohei <kaigai@kaigai.gr.jp>,
selinux@tycho.nsa.gov
Subject: Re: [RFC] SELinux and PostgreSQL (draft v2)
Date: Mon, 11 Sep 2006 12:22:29 -0400 [thread overview]
Message-ID: <45058D45.2090909@mindspring.com> (raw)
In-Reply-To: <200609111008.11243.russell@coker.com.au>
Russell Coker wrote:
> On Monday 11 September 2006 04:27, Joshua Brindle <method@gentoo.org> wrote:
>> You can do privilege separation in the database system via process
>> labels instead of only by dbms role. This is analogous to using fine
>> grained types to break up root privileges.
>
> Which also means that if two domains are not permitted to share data via files
> on disk then we can also be assured that they can't share data via the
> database. As we want to be able to analyse policy and prove that it meets
> our security goals this is quite important. Even if two users had different
> DBMS roles and the SE Linux access controls merely enforced the same access
> controls as the standard DBMS access control this would provide a benefit
> that would justify the existence of MAC support in the database for some
> users.
>
Thanks guys! It *will* add additional features (e.g. MLS) that are
unlikely to be included in the existing "roles and privileges".
This seems like the perfect use for a user space security server.
Any prognostication as to when that might appear?
Richard
--
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.
prev parent reply other threads:[~2006-09-11 16:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 9:49 [RFC] SELinux and PostgreSQL KaiGai Kohei
2006-09-07 12:52 ` Joshua Brindle
2006-09-07 13:24 ` Russell Coker
2006-09-07 13:54 ` Joshua Brindle
2006-09-07 14:07 ` Russell Coker
2006-09-07 14:15 ` Joshua Brindle
2006-09-07 15:06 ` KaiGai Kohei
2006-09-07 14:28 ` KaiGai Kohei
2003-12-01 23:07 ` Joshua Brindle
2006-09-07 15:52 ` KaiGai Kohei
2006-09-07 17:02 ` Joshua Brindle
2006-09-07 17:18 ` Joshua Brindle
2006-09-08 12:25 ` KaiGai Kohei
2006-09-08 12:25 ` KaiGai Kohei
2006-09-08 0:48 ` Russell Coker
2006-09-08 1:06 ` Joshua Brindle
[not found] ` <6FE441CD9F0C0C479F2D88F959B015883C1638@exchange.columbia.t resys.com>
2006-09-08 2:01 ` James W. Hoeft
2006-09-08 2:10 ` Joshua Brindle
2006-09-08 12:05 ` Russell Coker
2006-09-08 13:19 ` Joshua Brindle
2006-09-08 13:46 ` KaiGai Kohei
2006-09-08 2:04 ` Joshua Brindle
2006-09-08 12:25 ` KaiGai Kohei
2006-09-07 19:08 ` Richard Hally
2006-09-08 12:25 ` KaiGai Kohei
2006-09-10 4:55 ` [RFC] SELinux and PostgreSQL (draft v2) KaiGai Kohei
2006-09-10 7:08 ` Russell Coker
2006-09-11 12:10 ` KaiGai Kohei
2006-09-11 12:16 ` Joshua Brindle
2006-09-11 13:03 ` KaiGai Kohei
2006-09-11 22:42 ` Russell Coker
2006-09-10 17:49 ` Richard Hally
2006-09-10 18:27 ` Joshua Brindle
2006-09-11 0:08 ` Russell Coker
2006-09-11 16:22 ` Richard Hally [this message]
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=45058D45.2090909@mindspring.com \
--to=rhally@mindspring.com \
--cc=kaigai@kaigai.gr.jp \
--cc=method@gentoo.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.