From: Joshua Brindle <method@manicmethod.com>
To: Kohei Kaigai <Kohei.Kaigai@EMEA.NEC.COM>
Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>,
KaiGai Kohei <kaigai@ak.jp.nec.com>,
SE Linux <selinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: sepgsql and process transition
Date: Thu, 01 Sep 2011 14:36:05 -0400 [thread overview]
Message-ID: <4E5FD095.3020900@manicmethod.com> (raw)
In-Reply-To: <D0C1A1F8BF513F469926E6C71461D9EC0523B8@EX10MBX02.EU.NEC.COM>
Kohei Kaigai wrote:
<snip>
>> trusted procedures are not processes and should not use the process object class.
>>
> We may need to have an upper meta-level viewpoint.
>
> When a subject entity appeared in operating system, we call it "process".
> When a subject entity appeared in database system, we call it something like "db_client".
> And, a subject entity appeared in operating system tries to access database objects,
> its security label is dealt with "db_client" class. Hmm.
>
It isn't that surprising. When processes create sockets they are labeled as the
process label by default, files in /proc/<pid> are labeled as the process label.
Just because the label is the same doesn't mean the object class is.
--
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:[~2011-09-01 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 18:36 sepgsql and process transition Joshua Brindle
2011-08-30 20:48 ` Kohei KaiGai
2011-08-30 23:16 ` Joshua Brindle
2011-08-31 20:02 ` Joshua Brindle
2011-08-31 20:33 ` Kohei KaiGai
2011-09-01 9:33 ` Kohei Kaigai
2011-09-01 14:39 ` Joshua Brindle
2011-09-01 15:51 ` Kohei Kaigai
2011-09-01 18:36 ` Joshua Brindle [this message]
2011-09-01 19:13 ` Joshua Brindle
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=4E5FD095.3020900@manicmethod.com \
--to=method@manicmethod.com \
--cc=Kohei.Kaigai@EMEA.NEC.COM \
--cc=kaigai@ak.jp.nec.com \
--cc=kaigai@kaigai.gr.jp \
--cc=sds@tycho.nsa.gov \
--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.