From: Joshua Brindle <method@manicmethod.com>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>, KaiGai Kohei <kaigai@kaigai.gr.jp>
Cc: SE Linux <selinux@tycho.nsa.gov>, Stephen Smalley <sds@tycho.nsa.gov>
Subject: sepgsql and process transition
Date: Tue, 30 Aug 2011 14:36:42 -0400 [thread overview]
Message-ID: <4E5D2DBA.9060201@manicmethod.com> (raw)
Kaigai, I'm taking a look at the latest Postgresql master and I see that you are
using process:transition permission to check access to transition from one type
to another for trusted procedures.
Why didn't you add a transition permission to db_procedure? We are trying not to
reuse kernel object classes for userspace object managers these days (I know we
haven't been great about that in the past). I know this situation is a little
tricky because the beginning type is a process type (domain) and the ending type
is a procedure type, which closely maps to a domain type.
The beginning type may not always be a domain type though, if a procedure calls
another procedure, or if postgres user session types become derived types
(user_t -> sepgsql_user_t) we could completely divorce process types from
postgres types.
Stephen, do you have an opinion on this?
--
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 reply other threads:[~2011-08-30 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 18:36 Joshua Brindle [this message]
2011-08-30 20:48 ` sepgsql and process transition 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
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=4E5D2DBA.9060201@manicmethod.com \
--to=method@manicmethod.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.