All of lore.kernel.org
 help / color / mirror / Atom feed
From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: Andy Warner <warner@rubix.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: db_schema object class (and others)
Date: Tue, 09 Mar 2010 09:56:19 +0900	[thread overview]
Message-ID: <4B959CB3.9040309@ak.jp.nec.com> (raw)
In-Reply-To: <4B959214.90905@rubix.com>

(2010/03/09 9:11), Andy Warner wrote:
> Back in March of 2009 there was discussion regarding adding new database 
> object classes (e.g., db_schema) to policy. I have been keeping my eye 
> open for them but have not seen them. Can anyone give me a status of 
> this? If it has not be implemented, is there still interest if some 
> picks it up?

Right now, we are waiting for SELinux feature to be gotten upstreamed to
PostgreSQL, because here is a risk that we are forced to change definition
of the object class and permissions. :(

I also think the following object classes are necessary:
 - db_catalog (specific to rubix, it is a layer between database and schema)
 - db_schema
 - db_sequence
 - db_view

Currently, I'm reworking existing access control stuff in PostgreSQL
for the upcoming v9.1 development cycle, because it does not have clear
interface between the core and security server like LSM, so the patch
had been too large to merge at one for two years.

Thanks,
-- 
KaiGai Kohei <kaigai@ak.jp.nec.com>

--
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.

      reply	other threads:[~2010-03-09  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09  0:11 db_schema object class (and others) Andy Warner
2010-03-09  0:56 ` KaiGai Kohei [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=4B959CB3.9040309@ak.jp.nec.com \
    --to=kaigai@ak.jp.nec.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=warner@rubix.com \
    /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.