From: pebenito@ieee.org (Chris PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] xserver: Allow user fonts (and caches) to be mmap()ed.
Date: Wed, 3 Oct 2018 21:59:42 -0400 [thread overview]
Message-ID: <171b1f46-9231-27ee-d421-f43fd8cf454a@ieee.org> (raw)
In-Reply-To: <20181002200255.29926-1-aranea@aixah.de>
On 10/02/2018 04:02 PM, Luis Ressel via refpolicy wrote:
> Applications can optionally map fonts and fontconfig caches into memory.
> miscfiles_read_fonts() already grants those perms, but it seems
> xserver_use_user_fonts() was forgotten.
> ---
> policy/modules/services/xserver.if | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/policy/modules/services/xserver.if b/policy/modules/services/xserver.if
> index 1b25ff5c1..ec944672b 100644
> --- a/policy/modules/services/xserver.if
> +++ b/policy/modules/services/xserver.if
> @@ -506,11 +506,12 @@ interface(`xserver_use_user_fonts',`
>
> # Read per user fonts
> allow $1 user_fonts_t:dir list_dir_perms;
> - allow $1 user_fonts_t:file read_file_perms;
> + allow $1 user_fonts_t:file { map read_file_perms };
>
> # Manipulate the global font cache
> manage_dirs_pattern($1, user_fonts_cache_t, user_fonts_cache_t)
> manage_files_pattern($1, user_fonts_cache_t, user_fonts_cache_t)
> + allow $1 user_fonts_cache_t:file { map read_file_perms };
>
> # Read per user font config
> allow $1 user_fonts_config_t:dir list_dir_perms;
Merged.
--
Chris PeBenito
prev parent reply other threads:[~2018-10-04 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 20:02 [refpolicy] [PATCH] xserver: Allow user fonts (and caches) to be mmap()ed Luis Ressel
2018-10-04 1:59 ` 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=171b1f46-9231-27ee-d421-f43fd8cf454a@ieee.org \
--to=pebenito@ieee.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).