SELinux-Refpolicy Archive on lore.kernel.org
 help / color / Atom feed
From: Chris PeBenito <pebenito@ieee.org>
To: "Sugar, David" <dsugar@tresys.com>,
	"selinux-refpolicy@vger.kernel.org" 
	<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH 1/1 v2] grant rpm_t permission to map security_t
Date: Sat, 13 Jul 2019 14:08:39 -0400
Message-ID: <f3985d08-ef43-4487-47aa-e97dfecec175@ieee.org> (raw)
In-Reply-To: <20190709151527.13582-1-dsugar@tresys.com>

On 7/9/19 11:15 AM, Sugar, David wrote:
> type=AVC msg=audit(1560944462.698:217): avc:  denied  { map } for pid=1265 comm="rpm" path="/sys/fs/selinux/status" dev="selinuxfs" ino=19 scontext=system_u:system_r:rpm_t:s0 tcontext=system_u:object_r:security_t:s0 tclass=file permissive=1
> 
> v2 - Create new interface to allow mapping security_t and use this interface by rpm_t
> 
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
>   policy/modules/admin/rpm.te      |  1 +
>   policy/modules/kernel/selinux.if | 20 ++++++++++++++++++++
>   2 files changed, 21 insertions(+)
> 
> diff --git a/policy/modules/admin/rpm.te b/policy/modules/admin/rpm.te
> index 3c5968f9..082052fa 100644
> --- a/policy/modules/admin/rpm.te
> +++ b/policy/modules/admin/rpm.te
> @@ -185,6 +185,7 @@ selinux_compute_access_vector(rpm_t)
>   selinux_compute_create_context(rpm_t)
>   selinux_compute_relabel_context(rpm_t)
>   selinux_compute_user_contexts(rpm_t)
> +selinux_map_security_files(rpm_t)
>   
>   storage_raw_write_fixed_disk(rpm_t)
>   storage_raw_read_fixed_disk(rpm_t)
> diff --git a/policy/modules/kernel/selinux.if b/policy/modules/kernel/selinux.if
> index 6790e5d0..81d8f918 100644
> --- a/policy/modules/kernel/selinux.if
> +++ b/policy/modules/kernel/selinux.if
> @@ -635,6 +635,26 @@ interface(`selinux_compute_user_contexts',`
>   	allow $1 security_t:security compute_user;
>   ')
>   
> +########################################
> +## <summary>
> +##	Allows caller to map secuirty_t files.
> +## </summary>
> +## <param name="domain">
> +##	<summary>
> +##	Domain allowed access.
> +##	</summary>
> +## </param>
> +#
> +
> +interface(`selinux_map_security_files',`
> +	gen_require(`
> +		type security_t;
> +	')
> +
> +	dev_search_sysfs($1)
> +	allow $1 security_t:file map;
> +')
> +
>   ########################################
>   ## <summary>
>   ##	Unconfined access to the SELinux kernel security server.

Merged.

-- 
Chris PeBenito

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 15:15 Sugar, David
2019-07-13 18:08 ` Chris PeBenito [this message]

Reply instructions:

You may reply publically 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=f3985d08-ef43-4487-47aa-e97dfecec175@ieee.org \
    --to=pebenito@ieee.org \
    --cc=dsugar@tresys.com \
    --cc=selinux-refpolicy@vger.kernel.org \
    /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

SELinux-Refpolicy Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/selinux-refpolicy/0 selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ https://lore.kernel.org/selinux-refpolicy \
		selinux-refpolicy@vger.kernel.org selinux-refpolicy@archiver.kernel.org
	public-inbox-index selinux-refpolicy


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.selinux-refpolicy


AGPL code for this site: git clone https://public-inbox.org/ public-inbox