All of lore.kernel.org
 help / color / mirror / Atom feed
From: kaigai@ak.jp.nec.com (KaiGai Kohei)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] roles_dbadm.patch
Date: Fri, 27 Aug 2010 16:31:44 +0900	[thread overview]
Message-ID: <4C7769E0.1050605@ak.jp.nec.com> (raw)
In-Reply-To: <4C76EB3E.80903@redhat.com>

(2010/08/27 7:31), Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> http://people.fedoraproject.org/~dwalsh/SELinux/F14/roles_dbadm.patch
> 
> Add sudo for transition from staff.
> 
> I think this should not be a login domain.

| --- a/policy/modules/roles/dbadm.te
| +++ b/policy/modules/roles/dbadm.te
| @@ -21,7 +21,7 @@ gen_tunable(dbadm_read_user_files, false)
|
|  role dbadm_r;
|
| -userdom_base_user_template(dbadm)
| +userdom_unpriv_user_template(dbadm)
|
|  ########################################
|  #

The userdom_unpriv_user_template() contains userdom_login_user_template()
which allows dbadm_t performs as a login domain.
It is not what you intend, is it?

In the latest refpolicy, dbadm is declared with userdom_base_user_template().

| @@ -58,3 +58,7 @@ optional_policy(`
|  optional_policy(`
|  	postgresql_admin(dbadm_t, dbadm_r)
|  ')
| +
| +optional_policy(`
| +	sudo_role_template(dbadm, dbadm_r, dbadm_t)
| +')
| diff --git a/policy/modules/roles/guest.te b/policy/modules/roles/guest.te
| index 531c616..321e5a7 100644

Also, it was already merged in the latest refpolicy.

BTW, could you add the dbadm.pp into selinux-policy package?
IIRC, you concerned about dbadm_t is declared as login domain.

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

  reply	other threads:[~2010-08-27  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 22:31 [refpolicy] roles_dbadm.patch Daniel J Walsh
2010-08-27  7:31 ` KaiGai Kohei [this message]
2010-08-27 13:24   ` Daniel J Walsh
2010-08-27 13:27     ` Dominick Grift
  -- strict thread matches above, loose matches on Subject: below --
2010-02-23 19:38 Daniel J Walsh
2010-03-04 14:26 ` Christopher J. PeBenito

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=4C7769E0.1050605@ak.jp.nec.com \
    --to=kaigai@ak.jp.nec.com \
    --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.