All of lore.kernel.org
 help / color / mirror / Atom feed
From: kaigai@kaigai.gr.jp (KaiGai Kohei)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] services_postgresql.patch
Date: Sat, 23 May 2009 20:44:35 +0900	[thread overview]
Message-ID: <4A17E1A3.4010501@kaigai.gr.jp> (raw)
In-Reply-To: <4A16EC3A.70208@redhat.com>

Daniel J Walsh wrote:
> On 05/22/2009 10:51 AM, KaiGai Kohei wrote:
>> Daniel J Walsh wrote:
>>> http://people.fedoraproject.org/~dwalsh/SELinux/F11/services_postgresql.patch 
>>>
>>>
>>>
>>> Add _admin interface
>>> Type for init script,
>>>
>>> And I believe a couple of transtions to be to proc_t not proc_exec_t
>>
>> In the latest refpolicy, sepgsql_proc_t is an alias of 
>> sepgsql_proc_exec_t.
>> Other procedure types also have xxxx_sepgsql_proc_exec_t, so it should
>> follow the convension.
>>
>> Thanks,
> 
> ok.  Did not make much sense to me, you are creating executables?

Yes, db_procedure class objects are executable stuff.

We assume xxxx_proc_exec_t types are assigned to SQL procedures.
SQL procedures are invoked and executed as a part of SQL query,
and some of them (with sepgsql_trusted_proc_exec_t) can causes
domain transition during execution of the procedure.

It is an analogy of executable programs in database.

Thanks,
-- 
KaiGai Kohei <kaigai@kaigai.gr.jp>

  reply	other threads:[~2009-05-23 11:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 14:33 [refpolicy] services_postgresql.patch Daniel J Walsh
2009-05-22 14:51 ` KaiGai Kohei
2009-05-22 18:17   ` Daniel J Walsh
2009-05-23 11:44     ` KaiGai Kohei [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26 22:08 Daniel J Walsh
2010-09-15 13:21 ` Christopher J. PeBenito
2010-02-23 20:38 Daniel J Walsh
2009-11-12 21:51 Daniel J Walsh
2009-03-24 13:53 Daniel J Walsh
2008-09-24 20:11 Daniel J Walsh

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=4A17E1A3.4010501@kaigai.gr.jp \
    --to=kaigai@kaigai.gr.jp \
    --cc=refpolicy@oss.tresys.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.