All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris PeBenito <pebenito@ieee.org>
To: "Lawrence, Stephen" <slawrence@tresys.com>,
	SELinux Refpolicy <selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH 2/2] miscfiles: reading certs allows map permission also
Date: Thu, 26 Dec 2019 11:58:48 -0500	[thread overview]
Message-ID: <e97c86fd-98d5-e748-61bf-3d7245c37cbc@ieee.org> (raw)
In-Reply-To: <20191206192526.8129-3-slawrence@tresys.com>

On 12/6/19 2:25 PM, Lawrence, Stephen wrote:
> ---
>   policy/modules/system/miscfiles.if | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/policy/modules/system/miscfiles.if b/policy/modules/system/miscfiles.if
> index df11794a..4ff82afb 100644
> --- a/policy/modules/system/miscfiles.if
> +++ b/policy/modules/system/miscfiles.if
> @@ -107,6 +107,7 @@ interface(`miscfiles_read_all_certs',`
>   
>   	allow $1 cert_type:dir list_dir_perms;
>   	read_files_pattern($1, cert_type, cert_type)
> +	allow $1 cert_type:file map;
>   	read_lnk_files_pattern($1, cert_type, cert_type)
>   ')
>   
> @@ -128,6 +129,7 @@ interface(`miscfiles_read_generic_certs',`
>   
>   	allow $1 cert_t:dir list_dir_perms;
>   	read_files_pattern($1, cert_t, cert_t)
> +	allow $1 cert_t:file map;
>   	read_lnk_files_pattern($1, cert_t, cert_t)
>   ')

Needs a separate map or mmap_read interface.  I'm not aware of all cert 
reading requiring mmap.

-- 
Chris PeBenito

      reply	other threads:[~2019-12-26 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 19:25 [PATCH 0/2] Fixes to enable slapd to run Lawrence, Stephen
2019-12-06 19:25 ` [PATCH 1/2] ldap: various permissions required by slapd Lawrence, Stephen
2019-12-06 19:25 ` [PATCH 2/2] miscfiles: reading certs allows map permission also Lawrence, Stephen
2019-12-26 16:58   ` Chris PeBenito [this message]

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=e97c86fd-98d5-e748-61bf-3d7245c37cbc@ieee.org \
    --to=pebenito@ieee.org \
    --cc=selinux-refpolicy@vger.kernel.org \
    --cc=slawrence@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.